Tool reference
search_pages
search_pages finds the authenticated user’s stored ready Pages. It reads Landit data only and does not contact external enrichment sources.
MCPExample prompt
Use search_pages to find my existing Landit Pages created with
template [template-slug]. Return their links and recorded visit counts.
Follow pagination until you have all matching Pages.
Replace [template-slug] with the template slug you want to search by.
Arguments
All arguments are optional. Every supplied filter is combined with the others.
| Name | Type | Meaning |
|---|---|---|
page |
Integer, at least 1 | Result page; defaults to 1. |
created_from |
ISO 8601 date-time | Inclusive lower creation boundary. |
created_to |
ISO 8601 date-time | Inclusive upper creation boundary. |
slug |
Nonempty string | Exact Page slug. |
template_slug |
Nonempty string | Exact associated template slug. |
enrichment_name |
Nonempty string | Exact associated batch name. |
source |
String enum | csv file, homepage, public-api, extension, outreach, hubspot, or mcp. |
status |
Nonempty string | Exact status filter within the ready-Page scope. |
integration |
String enum | CRM provider; hubspot or outreach. Requires prospect_id. |
prospect_id |
Nonempty string | Exact provider record identifier. Requires integration. |
The legacy public-api source value is a search filter for existing records, not an officially supported API setup route. Because the base scope is ready Pages, use run-status tools for queued or failed generation; another status filter does not expand that scope.
{"template_slug": "selected-template", "page": 1}
Result
The response has items, current_page, next_page, total_pages, and total_count. Results contain at most 25 items per page, newest first. Follow next_page until null when completeness matters.
Each item includes slug, url, status, source, visit_count, template_slug, enrichment_name, created_at, and prospect_links. Each prospect link contains integration, nullable prospect_id, and integration_data_status (pending or available).
Errors
invalid_date rejects malformed timestamps. invalid_date_range means the lower boundary exceeds the upper boundary. invalid_prospect_filter means only one member of the integration/record pair was supplied. An empty result is otherwise valid; check combined filters before concluding no Page exists.