Skip to main content
Glama

Add pages to the site index

add_site_pages

Manually add page paths to the agent's website index (read immediately, kept through refreshes). Use for pages the crawler missed. Rate-limited to 60 adds/hour per user.

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": "add_site_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses persistence behavior ('read immediately, kept through refreshes') and a concrete rate limit ('60 adds/hour per user'). It does not state what happens on duplicate or invalid paths, which is the remaining gap for a mutation tool.

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?

Three short sentences with zero waste; the core action comes first, then the usage condition, then the operational constraint. Every sentence earns its place.

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?

For a two-parameter write tool with no annotations and no output schema, the description covers purpose, selection condition, persistence, and rate limiting — enough to invoke it correctly. Duplicate handling and the agent_id semantics are the only notable omissions.

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

Parameters3/5

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

Schema description coverage is 0%, so both parameters are undocumented in schema. The description clarifies that the array holds 'page paths' rather than full URLs, which adds real meaning, but agent_id is never mentioned and no format or example is given for paths.

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?

The description states a specific verb and resource: 'Manually add page paths to the agent's website index'. It implicitly distinguishes itself from crawler-driven indexing ('pages the crawler missed'), though it does not name a specific sibling tool like start_site_indexing or index_subdomain.

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?

'Use for pages the crawler missed' gives a clear selection condition for this tool over the automatic indexing path. It lacks an explicit when-not or a named alternative tool, but the intended context is unambiguous.

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