Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Audit sitemap indexing in Google

insights_index_audit
Read-only

Inspect many URLs and report which ones Google has not indexed. Pass either a sitemap (or sitemap index) URL or a list of URLs. Uses the property's URL Inspection quota (2,000 per day); page through long lists with offset.

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": {
      "siteUrl": "<siteUrl>"
    },
    "name": "insights_index_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoURLs to inspect, instead of a sitemap
limitNoURLs to inspect in this call (1-100). Defaults to 25.
offsetNoNumber of URLs to skip, for paging. Defaults to 0.
siteUrlYesSearch Console property exactly as gsc_list_sites returns it: "https://example.com/" or "sc-domain:example.com"
sitemapUrlNoPublic sitemap or sitemap index URL, e.g. https://example.com/sitemap.xml

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new context beyond them: it consumes the property's URL Inspection quota (2,000/day) and requires offset paging for long lists. It does not describe the shape of the report, but with no output schema that is a minor omission.

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 sentences, front-loaded with the outcome, then the input modes, then the quota/paging constraint. No filler and nothing repeated from the title or schema.

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 five-parameter, fully documented tool with no output schema, the description covers purpose, input modes, quota cost, and paging. It leaves undefined what happens if both urls and sitemapUrl are supplied, and does not say whether indexed URLs appear in the output.

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 adds the either/or relationship between sitemapUrl and urls that the schema only hints at with "instead of a sitemap." It also reinforces offset as the paging mechanism, giving the agent a clearer mental model than the schema alone.

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 opens with a specific verb and resource: "Inspect many URLs and report which ones Google has not indexed." The word "many" implicitly separates it from the single-URL sibling gsc_inspect_url, though no sibling is named explicitly, which keeps it 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?

It gives clear selection guidance for the two input modes: "Pass either a sitemap (or sitemap index) URL or a list of URLs," and adds the operational rule to page long lists with offset. It never names an alternative tool or states when not to use this one, so it stops short of full routing guidance.

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

All mowteng toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources