Skip to main content
Glama

Pumpkin

search_site_pages

Read-only

Find published pages. Cite the returned title and URL.

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": {
      "site": "<site>",
      "query": "<query>"
    },
    "name": "search_site_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
limitNo
queryYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond the structured data: results are restricted to published pages, and the payload carries at least title and URL. It says nothing about result counts, pagination, or empty-result behavior.

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

Conciseness4/5

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

Two short sentences with no filler and the core behavior front-loaded. It is efficient, though the terseness edges into under-specification rather than tightness.

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?

With four parameters, 25% schema coverage, and no output schema, the description should carry the weight on query semantics and pagination, yet it only covers the read-only/published aspect. An agent cannot tell how to page or how results are ordered from this definition.

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

Parameters2/5

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

Schema description coverage is only 25% – the schema documents `site` but leaves `query`, `limit`, and `offset` bare. The description does not compensate: it never mentions that a free-text query is required, nor how limit/offset govern paging through results.

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?

"Find published pages" gives a verb and a resource with a useful qualifier (only published pages), which is more than a restatement of the name. However, it omits that this is a site-scoped query search, and it never distinguishes itself from the sibling read_site_page, so an agent must infer the difference from the name alone.

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?

There is no when-to-use guidance and no named alternative; "Cite the returned title and URL" is an instruction about handling results, not about when to choose this tool over read_site_page or site_get. An agent gets no selection criteria from the description.

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