Skip to main content
Glama

OnPage.dev

by dev.onpage
OverviewDiscussionsAdmin

XML sitemap

sitemap
Read-onlyIdempotent

The XML sitemap. Pick with mode: check = Check the sitemap and a sample of its URLs. Needs url. generate = Write a sitemap from a page list or audit. Needs audit_id.

Input Schema

NameRequiredDescriptionDefault
urlNoThe site's home page, or the sitemap URL itself.
modeNoDefault check.
detailNobrief = short summary.
audit_idNoA finished site audit.
memory_keyNosite_memory key, records this call.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / description
      Removed value: -"The result as structured data; fields depend on mode."
  2. Changed2 schema fields changed
    • changedInput schema / properties / detail / description
      Previous value: -"brief returns a short summary, default full."New value: +"brief = short summary."
    • changedInput schema / properties / memory_key / description
      Previous value: -"Optional site_memory key, to record this call in the site memory."New value: +"site_memory key, records this call."
  3. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "brief returns a short summary, default full.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / memory_key
      Added value: +{
+  "description": "Optional site_memory key, to record this call in the site memory.",
+  "maxLength": 80,
+  "type": "string"
+}
  5. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful behaviour (check samples the sitemap's URLs; generate derives a sitemap from a page list or a finished audit), but it doesn't resolve the tension between 'Write a sitemap' and readOnlyHint=true — it should say the generated sitemap is an artifact returned to the caller rather than a change to the site. No rate limits, no side effects, no auth requirements stated.

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 clauses, mode selection front-loaded, zero filler. Every sentence carries routing information an agent can act on.

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?

With an output schema present, return values need not be described, and the mode/parameter contract is fully covered. Minor gaps remain around the detail flag's effect and around how generate relates to site_audit, but for a two-mode tool with 100% schema coverage this is close to sufficient.

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, but the description goes beyond the schema by mapping modes to the parameters they require (url for check, audit_id for generate) — information the schema's terse 'Default check.' does not convey. It still says nothing about detail, memory_key, or the url-vs-sitemap-URL distinction beyond what the schema already contains.

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 mode definitions supply real verbs and resources: 'check = Check the sitemap and a sample of its URLs' and 'generate = Write a sitemap from a page list or audit.' An agent can tell this is a two-mode sitemap tool. However, the tool is not distinguished from nearby siblings such as site_audit, robots_txt, or llms_txt, so it falls 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 Guidelines4/5

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

The description gives explicit mode-selection guidance with the triggering parameter for each branch ('check ... Needs url', 'generate ... Needs audit_id'), which is exactly what an agent needs to route a request. It stops at context though — there is no when-not-to-use and no pointer to an alternative sibling when the sitemap is not the right target.

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

All OnPage.dev toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources