Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Coverage Tool

adataforseo.coverage

Compare sitemap pages against Google site: results to identify unindexed pages, with each gap mapped to its source document for quick audit and fixes.

Instructions

Read-only. Index coverage of this site: pages in the sitemap vs pages Google returns for site:, and the list of pages that are not indexed, each mapped to its document.

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": "adataforseo.coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A3.6/5.0
Behavior3/5

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

Annotations are empty, so the description carries the burden, and it does declare 'Read-only' and describes the shape of what is returned (coverage comparison plus a non-indexed page list mapped to documents). It omits how site scope is determined, whether results come from a cached crawl or a live fetch, and any cost/latency expectations.

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?

One compact sentence plus a leading 'Read-only.' marker, front-loading the safety signal before the payload description. Dense but no filler; only minor cost is the somewhat run-on enumeration of the three outputs.

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 parameters and no output schema, the description explains all three returned data components well enough to call the tool. The remaining gap is scope and freshness (which site, how current the index comparison is), which matters for a diagnostic tool but is secondary.

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 no schema meaning to supplement; the description's implicit statement that the site is fixed by context is adequate. Baseline 4 applies for a parameterless tool.

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 comparison: sitemap page count vs. Google `site:` index count, plus an explicit non-indexed page list mapped to documents. That is far more concrete than a sibling like `adataforseo.audit` or `adataforseo.rankings`, though it never explicitly contrasts itself with those siblings.

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: an agent can infer this is the tool for checking indexation gaps, but there is no statement of when to prefer it over `adataforseo.audit` or `adataforseo.serp`, and no prerequisites (site scope, auth, freshness) are mentioned.

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