Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_indexation_summary

Get index-coverage totals for a property: known sitemap URLs, how many Google indexes, indexed percentage and a by-state breakdown with true prev/delta comparisons over a preset or custom date range.

Instructions

Index-coverage summary for a property: known (sitemap-submitted) URLs, how many Google indexes, indexed_pct and a by_state breakdown (Submitted and indexed, Crawled – currently not indexed, Discovered – currently not indexed, Excluded by 'noindex', Page with redirect, Not found 404, Soft 404…). indexed carries a true prev/delta; date range via preset or absolute from/to.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_indexation_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.4/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 of behavioral disclosure. It usefully describes return contents, state categories, and that 'indexed carries a true prev/delta', but it does not state read-only behavior, required permissions, rate limits, or error handling.

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?

The description is front-loaded with the main purpose and then lists the return components efficiently. It is dense and the parenthetical list of by_state values is long, but every sentence contributes information rather than repeating the tool name or title.

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?

Given zero parameters, no annotations, and no output schema, the description is fairly complete about what is returned: known URLs, indexed count, indexed_pct, by_state breakdown, prev/delta semantics, and date-range controls. It still omits explicit usage against siblings and safety/permission details, but covers the core return semantics an agent needs to invoke it.

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?

The schema declares zero parameters, so the baseline is 4. The description adds that date range can be set via preset or absolute from/to, which is useful semantic context, though those inputs are not explicitly represented in the schema and could create ambiguity.

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 resource and scope: 'Index-coverage summary for a property', then enumerates the key contents such as known sitemap URLs, indexed count, indexed_pct, and a by_state breakdown. It is clear what the tool returns, but it does not explicitly differentiate itself from sibling tools like get_indexation_history or get_gsc_summary.

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

Usage Guidelines2/5

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

The description contains no explicit guidance on when to use this tool versus alternatives. It mentions date-range configuration, but does not name sibling tools or state when this summary should be preferred over get_indexation_history or other index-related summaries.

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

Deploy Server

Other Tools