Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_discover_summary

Retrieve Discover clicks, impressions, and CTR for a date range, each compared with the preceding equal-length window via current, previous, delta, and percent-change values.

Instructions

Discover clicks, impressions and CTR for the range, each compared with the equal-length window immediately before it: *_current, *_prev, *_delta and *_change_pct (ctr is a 0–1 fraction). Discover carries no query, position, country or device breakdown, so none is returned.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose non-obvious behavior: the exact comparison baseline (equal-length window immediately preceding), the field-naming contract (*_current, *_prev, *_delta, *_change_pct), and the unit convention (ctr is a 0–1 fraction). Those details prevent misinterpretation of the returned numbers. It stops short of stating read-only safety, rate limits, or what happens when the range has insufficient history.

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?

Two compact sentences with zero padding: the first front-loads what is measured and how it is compared, the second front-loads the limitation. The field-name and unit conventions are packed into a parenthetical rather than a separate clause, so nothing is wasted.

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 annotations and no output schema, the description must explain the returned shape, and it does so via the field-name pattern and the CTR unit, which is the highest-value information an agent needs here. Completeness is only marginally reduced by the absence of guidance on range selection and on what happens with sparse or missing history.

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 at the input level; the baseline for an empty parameter set is 4. The description wisely spends its space on output-field semantics instead. The only gap is that it doesn't explain how the implicit date range is determined.

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 the resource (Discover) and the exact metrics delivered (clicks, impressions, CTR) plus the comparison basis (equal-length preceding window). It further scopes the tool by stating which dimensions are NOT carried (query, position, country, device), which helps separate it from breakdown siblings such as get_discover_top_pages without naming them. The verb is implied by the metric list rather than stated as 'returns', which keeps it just short of a 5.

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 negative scoping ('no query, position, country or device breakdown, so none is returned') implicitly tells the agent to reach for another tool when a breakdown is needed, but no alternative is named and no 'when to use' condition is stated. It also never says where the date range comes from, which matters for a zero-parameter tool. Usage is inferable but not directed.

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