Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delivery_search

Read-only

Search published website content as visitors see it, in one locale, using full-text search over item names and public fields. Returns matching items and total count; private fields are excluded.

Instructions

Full-text search over the website's content (item names + public field text) in one locale, as visitors would search it: published only (unless preview), private fields never matched or returned. Returns { items, total }. To find content for editing, list_pages or tree are usually faster.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoSite slug or id to act in (multisite). Omit to use this server's default site. Call list_sites to see what exists — an empty tree or search usually means the wrong site, not missing content.
typeNoOnly return items of this content type.
limitNoMax results, 1-100.
queryYesWords to search for, e.g. 'pricing plans'.
localeNoLocale code. Omit for the document's own locale (its site-default variant, else its only variant).
previewNotrue = read the latest drafts as the preview pane shows them (needs site-wide read access). Default false: published content only, exactly what visitors get.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.3
    • addedInput schema / properties / limit / description
      Added value: +"Max results, 1-100."
    • addedInput schema / properties / preview / description
      Added value: +"true = read the latest drafts as the preview pane shows them (needs site-wide read access). Default false: published content only, exactly what visitors get."
    • addedInput schema / properties / query / description
      Added value: +"Words to search for, e.g. 'pricing plans'."
    • addedInput schema / properties / type / description
      Added value: +"Only return items of this content type."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: only published content is matched unless preview, private fields are never matched or returned, and the return shape is { items, total }. It doesn't disclose pagination or result-ordering behavior, which keeps it below a 5.

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

Conciseness5/5

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

Two sentences with zero padding. The core scope and constraint are front-loaded, and the routing hint to siblings is placed last where it belongs.

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

Completeness5/5

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

No output schema exists, and the description compensates by stating the return shape. Combined with published-only/private-field behavior, locale scoping, and the preview-access caveat, an agent has everything needed to call this correctly for a read-only search tool.

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 earns above it by explaining what the query actually matches against (item names and public field text) and that search is scoped to a single locale, which meaningfully qualifies the query and locale parameters beyond the schema's wording.

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 (full-text search) and resource (website content: item names + public field text), plus scope constraints (one locale, published only unless preview, private fields excluded). It also names the sibling tools it is not (list_pages, tree), so an agent can route without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes away from this tool for editing use cases: 'To find content for editing, list_pages or tree are usually faster.' That names alternatives and the condition selecting them. It lacks a positive 'use this when' framing (e.g. visitor-facing lookup), but the scope statement covers most of that implicitly.

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

Deploy Server

Other Tools