Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_discover_top_pages

Retrieves a property's top Discover pages ranked by clicks, impressions, or CTR with metrics, period-over-period changes, and cursor pagination for SEO reporting.

Instructions

The property's top Discover pages ranked by clicks — or by impressions or CTR — each with its clicks, impressions and ctr for the range and the change against the preceding window. Cursor-paginated via next_cursor.

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

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?

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses the returned metrics (clicks, impressions, ctr), that each carries a change against the preceding window, and that results are cursor-paginated via next_cursor. It omits the default ranking, ordering tie-breaks, and any limits on result volume, which keeps it short of a 5.

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 dense sentences with the resource and scope front-loaded, the alternative rankings attached inline, and pagination placed last. No filler and nothing restated from the title or schema.

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, and the description compensates by enumerating the returned fields and the comparison window, so an agent knows what comes back. The main unresolved item is how the ranking metric and cursor are actually supplied given the empty input schema, which a complete definition would state.

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 input schema declares zero parameters, so the baseline is high. The description introduces concepts the empty schema does not expose — a choice of ranking metric and a next_cursor — which is useful, though it is ambiguous whether those are call arguments or response fields, a gap the schema cannot resolve.

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?

States a specific verb and resource ('top Discover pages ranked by clicks… or by impressions or CTR') and scopes it to the property and range. It is clearly a Discover-specific ranked-pages tool, though it never names how it differs from the sibling get_top_pages, leaving that distinction to inference.

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 implied by the framing ('the property's top Discover pages… for the range'), so an agent can infer it is the Discover leaderboard call. There is no explicit when-to-use versus get_discover_summary or get_top_pages, and no statement of prerequisites or 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