Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_indexation_history

Retrieves the daily indexed-pages trend across a property's sitemaps as date/value points for time-series charts, and flags when too few days exist to chart meaningfully.

Instructions

The daily indexed-pages trend — one "indexed" series of {date, value} points, summed across the property's sitemaps and ready for a time-series chart. Returns points (days with real data) and flags insufficient_history when there are too few days to chart meaningfully.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the aggregation rule ('summed across the property's sitemaps'), the return shape ({date, value} points), and an edge-case behavior ('flags insufficient_history when there are too few days'). It does not state read-only status explicitly or anything about data freshness, permissions, or caching, which is the remaining gap.

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?

Two sentences, front-loaded with what the series is before the return-shape and edge-case detail. Slightly dense with quoted literals ('indexed', {date, value}) but each element adds information; nothing is filler.

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?

There is no output schema, so the description must explain the return value, and it does — series shape, aggregation scope, and the insufficient_history flag. For a zero-parameter read tool this is close to sufficient; only freshness/recency expectations are left unstated.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description's mention of property-level summation implicitly clarifies the implicit scope of the call.

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 names a specific resource and shape: 'the daily indexed-pages trend — one "indexed" series of {date, value} points.' That is clearly a time-series history rather than a snapshot summary, so an agent can distinguish it from get_indexation_summary or list_indexation_pages by intent. It stops short of naming those siblings 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?

Usage is only implied: the phrase 'ready for a time-series chart' signals the charting/trend use case, and the insufficient_history flag hints at a small-data caveat. There is no explicit when-to-use versus when-to-prefer-a-summary statement and no mention of preconditions.

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