Skip to main content
Glama

SEO Rank Fixer

Index status

index_status
Read-onlyIdempotent

Which of a site's pages are in Google's index, from Google's URL Inspection, and why the others are not: not indexed, blocked by robots.txt, noindex, unreadable, or indexed under a different URL, with Google's status, sitemap and crawl dates for each problem page.

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": {
      "siteId": "<siteId>"
    },
    "name": "index_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real value beyond that: it discloses the data provenance (Google's URL Inspection, i.e., externally sourced Google data rather than an internal crawl) and, since there is no output schema, describes what each result carries (Google's status, sitemap and crawl dates per problem page). It stops short of noting latency or inspection quotas, which matters for a URL Inspection-backed call.

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?

A single sentence that front-loads the answer (which pages are indexed) before the failure taxonomy. It is dense but each clause carries information; the trailing "with Google's status, sitemap and crawl dates" is arguably a second thought bolted on with a comma rather than a period.

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 no output schema, the description does the work of telling the agent what comes back (per-page index verdict plus Google status, sitemap and crawl dates). It is nearly complete for a one-parameter read tool; only the scope of pages inspected and any inspection-rate constraints are unaddressed.

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?

There is only one parameter and schema coverage is 100%, with the schema already stating it is "A site id from list_sites." The description adds no additional meaning about siteId (e.g., whether it scopes to a single property vs. domain property). Baseline 3 applies when the schema does the heavy lifting.

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?

"Which of a site's pages are in Google's index, from Google's URL Inspection, and why the others are not" names the exact resource (index status of a site's pages), the data source, and enumerates the outcome categories (robots.txt, noindex, unreadable, alternate URL). That is far more specific than a tautology, and it implicitly separates this diagnostic from the audit/report siblings, 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 enumeration of indexation failure reasons strongly implies the diagnostic use case, but there is no explicit "use this when... instead of site_audit / scan_page" routing, and no stated prerequisites beyond the siteId requirement. Guidance is inferable rather than stated.

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.