Skip to main content
Glama

Remove pages from the site index

exclude_site_pages

Remove pages from the agent's website index (they stay out through refreshes). undo=true brings removed pages back.

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>",
      "paths": "<paths>"
    },
    "name": "exclude_site_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
undoNo
pathsYes
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose two real behaviors — removals persist across refreshes and undo=true reverses them — which is genuine value beyond the schema. It omits permissions/auth needs, whether removal is idempotent, the 200-path cap, and what happens to unknown paths.

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 short sentences, zero filler, with the core action front-loaded and the persistence caveat and undo behavior following immediately.

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?

A mutating tool with no annotations and no output schema needs more than this, but the description does cover the two hardest questions (durability of removal and reversibility). Gaps remain on parameter meaning, auth, and the effect of partial/invalid path input.

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 coverage is 0%, so the description must explain all three parameters. It only explains 'undo' meaningfully; 'paths' (array of what — URLs, path fragments, up to 200) and 'agent_id' are left entirely to the schema, which has no descriptions.

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?

States a specific verb and resource ('Remove pages from the agent's website index') and adds a scope nuance about persistence. It is clearly distinct from add_site_pages and list_site_index_pages, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

The removal intent is implied clearly enough that an agent can pick it over the sibling add/list tools, but there is no explicit when-to-use guidance, no prerequisite statement, and no mention of what to do if a path is not currently indexed.

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