Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_indexation_pages

Lists URLs by Google coverage state (as reported by get_indexation_summary) to audit indexing status, canonical mismatches, crawl dates, and discovery source.

Instructions

The URLs currently in a given Google coverage state (pass the state exactly as get_indexation_summary reports it). Each row returns url, state, last_crawled, google_canonical vs declared_canonical and discovered_via (sitemap or referring page). Cursor-paginated (limit max 200).

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": "list_indexation_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the load and does reasonably well: it discloses the returned columns (url, state, last_crawled, canonical comparison, discovered_via) and the cursor pagination with a limit ceiling of 200. It does not state permissions/auth needs or whether results are ordered, and 'list' only implicitly signals a read-only operation.

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 what the tool returns, then row shape, then pagination constraints. No filler, and the calling convention for the state argument is placed before the return detail.

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?

No output schema exists, and the description steps in to enumerate the row fields, which is exactly the missing piece. The residual gap is pagination mechanics (where the cursor comes from, when to stop looping) and the fact that the state/limit/cursor arguments are described but absent from the declared schema.

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 (open object), so baseline is 4; the description compensates by naming the state argument, insisting on the exact string produced by get_indexation_summary, and giving the limit ceiling and cursor paging. It never explains how a cursor is obtained or whether paging is automatic, which keeps it below 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('The URLs currently in a given Google coverage state') with the qualifier that separates it from the aggregate sibling get_indexation_summary. An agent can tell this is the per-URL drill-down rather than the summary.

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?

Gives an explicit sequencing rule: call get_indexation_summary first and pass the state exactly as it reports it, which prevents invalid state strings. It stops short of naming when-not-to-use or what to do for other indexation questions (e.g., history), so it is clear context without exclusions.

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