Skip to main content
Glama

findPages

Editor-curated marketing pages. Call listAvailableBlocks first to learn the available layout-block types. Title is required in default-locale. Use _status="draft" until reviewed, then _status="published" to go live NOW. To publish (or unpublish) at a FUTURE date, use the schedulePost tool with publishAt/unpublishAt — do NOT set a future publishedAt (the page stays a draft until the scheduled time, then auto-publishes). HOMEPAGE convention: set slug="home" (hardcoded in frontend route, EVERY locale needs slug="home"). System-pages use systemPageKey field — read-only in MCP. After page creation, link them in menus collection (slug="header-main") so they appear in navigation. INCOMING LINKS while unpublished: only link an anchor phrase that already exists in a published text (no new sentence, no rewording; new referring sentences only on publication day). pages collection. Drafts: yes (publish workflow; a find WITHOUT draft:true returns the published main-table state only). Public read: yes via /api/agents. MCP capabilities: find, create, update, delete. ⚠ delete is PERMANENT (hard-delete; the admin Trash does NOT catch MCP deletes). Write ONE document at a time: wait for the response of each create/update/delete call before sending the next — parallel writes can fail with a database deadlock (HTTP 500, nothing saved; retry that call alone). Before writing public text here, call getWritingGuidelines with this collection and the locale (brand voice, writing rules, fixed terms, SEO rules, taken keywords, field rules). Fields: title (localized), slug (localized), layout (blocks, localized), systemPageKey (enum: faq (FAQ index)|search (Search results)|posts-archive|glossary-archive|not-found (404 — page not found)|server-error (500 — server error)|+7), publishedAt (date), robots (enum: index (Index (default))|noindex (noindex (hide))), searchText (textarea, localized, ≤60000 chars, redacted), meta (group: title, description, focusKeyword, secondaryKeyword1-4, searchIntent, eeatInsight, image — localized). Layout blocks (39): hero, trustMarquee, statement, cardGrid, quotes, splitKi, codeFiles, splitMcp, capabilities, splitSprachen, coreScrolly, stackChips, fundament, teamAbout, faqBlock, cta, factsBand, pageHeader, featureList, compareTable, race, contactSplit, geoMap, eigenbau, legal, textContent, archive, mediaBlock, gallery, formBlock, newsletterBlock, snippetEmbed, testimonialsBlock, mediaText, cards, searchClient, html, styledHtmlBlock, datasetCitation. Use listAvailableBlocks for per-block field schemas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "findPages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional: specific document ID to retrieve. If not provided, returns all documents
pageNoPage number for pagination (default: 1)
sortNoField to sort by (e.g., "createdAt", "-updatedAt" for descending)
depthNoHow many levels deep to populate relationships (default: 0)
draftNoOptional: Whether the document should be queried from the versions table/collection or not.
joinsNoOptional: configure join field queries, or pass false to disable all join fields.
limitNoMaximum number of documents to return (default: 10, max: 100)
trashNoOptional: include soft-deleted documents when trash is enabled on the collection
whereNoOptional JSON string for where clause filtering (e.g., '{"title": {"contains": "test"}}')
localeNoOptional: locale code to retrieve data in (e.g., "en", "es"). Use "all" to retrieve all locales for localized fields
selectNoOptional: define exactly which fields you'd like to return in the response, e.g., {"title": true}
populateNoOptional: control which fields to include from populated relationship or upload documents.
paginationNoOptional: set to false to skip the count query overhead
fallbackLocaleNoOptional: fallback locale code to use when requested locale is not available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / joins
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {},
      +      "type": "object"
      +    },
      +    {
      +      "const": false,
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Optional: configure join field queries, or pass false to disable all join fields."
      +}
    • addedInput schema / properties / pagination
      Added value: +{
      +  "description": "Optional: set to false to skip the count query overhead",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / populate
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Optional: control which fields to include from populated relationship or upload documents.",
      +  "type": "object"
      +}
    • addedInput schema / properties / select / additionalProperties
      Added value: +{}
    • changedInput schema / properties / select / description
      Previous value: -"Optional: define exactly which fields you'd like to return in the response (JSON), e.g., '{\"title\": true}'"New value: +"Optional: define exactly which fields you'd like to return in the response, e.g., {\"title\": true}"
    • changedInput schema / properties / select / type
      Previous value: -"string"New value: +"object"
    • addedInput schema / properties / trash
      Added value: +{
      +  "description": "Optional: include soft-deleted documents when trash is enabled on the collection",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the behavioral burden. It usefully discloses draft-query semantics and public read access, but much of its behavioral content concerns writes (hard delete, deadlock retries, publish workflow) and it does not explain the find response shape or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a long collection manual rather than a focused tool definition, with creation fields, layout blocks, write warnings, and publishing conventions crowded around a find operation. It is not front-loaded with what findPages does and contains substantial material that does not help an agent invoke this tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter find tool with no output schema and no annotations, the definition should clarify query behavior and response expectations. Instead it spends most of its space on page authoring and layout-block rules, leaving gaps around filtering, pagination, relationship population, and what a find returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all 14 find parameters are already documented in the schema. The description adds meaningful detail for draft (published main-table state when false) and localization context, but says little about where, sort, select, populate, or depth beyond the schema's own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with the noun phrase 'Editor-curated marketing pages' rather than clearly stating that findPages retrieves or lists pages; the actual find behavior is buried in 'MCP capabilities: find, create, update, delete' and the draft note. It never distinguishes findPages from sibling find tools such as findPosts, so an agent gets only a vague sense of the tool's specific purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Most guidance concerns page creation and publishing (call listAvailableBlocks, use _status, schedulePost for future dates, link menus), not when to call findPages. The only find-specific hint is that omitting draft:true returns published main-table state; there is no explicit when/when-not guidance or alternative for querying pages versus other collections.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources