Skip to main content
Glama

Site index pages

list_site_index_pages

Every page of the agent's website index: language, title, text length, failures with error + attempt count, pages removed by the owner, manually added pages. Read-only, free.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "list_site_index_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two useful traits: the operation is read-only and incurs no cost. It also reveals that failed pages come with an error message and attempt count, which is genuinely informative. It says nothing about result size, pagination, ordering, or whether large indexes are truncated, which are the main behavioral risks for a full-listing tool.

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?

One compact sentence with the resource stated first and the returned fields enumerated after, so nothing is buried. The trailing "Read-only, free" is terse but earns its place as a cost/safety signal.

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

Completeness3/5

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

For a one-parameter list tool with no output schema and no annotations, the description does a reasonable job by enumerating the returned data categories, including the non-obvious failure and owner-removed entries. It is still incomplete on pagination, result ordering, and any precondition tying it to the indexing lifecycle.

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?

The single parameter agent_id has 0% schema description coverage, so the schema explains nothing. The phrase "the agent's website index" weakly implies the parameter selects which agent's index is read, but the description never names or explains agent_id, its format, or what happens if it is invalid.

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

Purpose4/5

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

"Every page of the agent's website index" names a specific resource and scope, and the field list (language, title, text length, failures, removed pages, manually added pages) makes the content concrete. It does not explicitly contrast itself with siblings like get_site_index_status or start_site_indexing, so it lands short of a 5.

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?

"Read-only, free" implies the call is cheap and safe to make, which is a mild usage signal. There is no statement of when to use this versus get_site_index_status or the add/exclude tools, and no preconditions such as whether indexing must be complete first.

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