Total CMS

search_collection

Read-onlyIdempotent

Free-text search within a single collection. Returns matching items decorated with a public url; total reflects what was found. Supports AND (default), OR, and "quoted phrases". Searches across the properties listed in the catalog below — other schema properties exist on objects but are not searchable here; use get_object for the full record or describe_collection to see every property. This tool does not filter by field value — use query_collection with include/exclude for that. Drafts are auto-hidden from anonymous callers.

Available collections and filterable properties:

articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable)
comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable)
extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)
guides — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable), kind (select), product (select)
releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle)
showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)
starters — id (id, sortable), name (text), job (text), useCase (select), siteName (text), summary (textarea), status (select), package (text), buildCommand (text), coreStarter (select), minEdition (select), minVersion (text), demoUrl (url), repoUrl (url), featured (toggle), draft (toggle), updated (datetime, sortable)
streams — id (id, sortable), title (text), date (date, sortable), summary (textarea), release (select), draft (toggle)
studio-app — id (id, sortable), summary (textarea)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection": "<collection>",
      "query": "<query>"
    },
    "name": "search_collection"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum items to return (capped at 50 to fit MCP response-size budgets).
`query`	Yes	Search terms. AND-semantics by default; use `or` between terms for OR; wrap phrases in double quotes.
`format`	No	Output format for styledtext properties on the matched items. markdown is friendliest for AI consumption.	markdown
`locale`	No	BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today.
`collection`	Yes	Collection id to search within. Use list_collections to discover available collections.

Output Schema

Name	Required	Description
`items`	Yes	Matched objects, each a flat field map decorated with a `url`. Field set varies by collection.
`limit`	Yes	Applied result cap.
`query`	Yes	The query that was run.
`total`	Yes	Number of items returned.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding what they don't say: drafts are auto-hidden from anonymous callers, only catalog-listed properties are searchable while other schema properties are not, and AND/OR/phrase semantics govern matching. The remaining gap is ordering — the catalog marks fields as "sortable" without saying whether this tool sorts results or in what order they come back.

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

Conciseness3/5

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

The two opening sentences are tight and front-loaded, but the bulk of the description is a nine-collection catalog annotated with "sortable", "toggle", "range", and "select" markers — filtering and sorting metadata for a tool that explicitly does not filter or sort. That bulk is partly relevant (searchable text fields) but substantially transferable to query_collection.

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

Completeness4/5

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

With a full output schema, rich annotations, and 100% schema coverage, the description only needs to cover selection and search scope, which it does. A small ambiguity remains: it lists non-text fields like id, url, and toggle as catalog properties without clarifying which of those free-text search actually matches.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by enumerating which properties are actually searchable per collection, which directly disambiguates what `query` can match against. Query syntax is largely restated from the schema's own description and examples, which limits the added value to mostly the searchable-field catalog.

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

Purpose5/5

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

States a specific verb and resource ("Free-text search within a single collection") plus what it returns ("items decorated with a public `url`; total reflects what was found"). It explicitly separates itself from query_collection, get_object, and describe_collection, so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit negative guidance ("This tool does not filter by field value — use query_collection with `include`/`exclude` for that") and names two alternatives with the conditions that select them (get_object for full records, describe_collection for the full property list). It also flags the anonymous-caller draft behavior, which affects whether a call is worth making.

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

All Total CMS tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.