Flinty

Top Pages

get_top_pages

Idempotent

Google Search Console breakdown by page (clicks, impressions, average position) for a window, each row resolved to its published article when the URL is a blog article. Queries Google live for the exact window (not the cumulative snapshot cache). Default window is the last 30 days ending yesterday; pass period ('7d'/'30d'/'90d') or explicit start_date/end_date (YYYY-MM-DD).

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

Input Schema

Name	Required	Description
`limit`	No	Max pages to return (1-100, default 10)
`period`	No	'7d', '30d' or '90d' (default '30d') — ignored if start_date/end_date are given
`end_date`	No	Window end, YYYY-MM-DD
`start_date`	No	Window start, YYYY-MM-DD

Output Schema

Name	Required	Description	Default
`pages`	Yes
`since`	No
`until`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Adds real context beyond annotations: a live Google query rather than a cached snapshot, a default 30-day window ending yesterday, and per-row article resolution. It does not explain the one surprising annotation, readOnlyHint=false, for what reads as a retrieval tool — an agent gets no hint about quota costs, external API calls, or why the call is not treated as read-only.

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?

Three sentences, front-loaded with the resource and metrics before the mechanics. The final sentence partly restates schema defaults (period values, date format), which is mild redundancy but keeps the definition self-contained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers what remains: live vs cached sourcing, default window semantics, and article resolution. For a zero-required-parameter reporting tool this is sufficient to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 and the schema already documents limit, period, and the date fields with formats. The description adds marginal meaning by anchoring the default window to 'last 30 days ending yesterday', which the schema does not state, but otherwise repeats the period values and YYYY-MM-DD format.

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: a Google Search Console breakdown by page with the exact metrics returned (clicks, impressions, average position), plus the extra behavior that rows are resolved to published articles. It is clear enough to separate from siblings like get_metrics or list_page_audits, though it never names a sibling to contrast against.

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 rather than prescribed: the mention that it queries Google live for the exact window '(not the cumulative snapshot cache)' hints at when this is preferred, and the default window is spelled out. There is no explicit when-to-use/when-not or named alternative such as get_metrics, so an agent must infer the choice.

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

All Flinty tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?