GSC Magic

Low-CTR pages for their position

report_ctr_outliers

Read-only

Pages whose CTR is under half of your site's median CTR at the same position: candidates for better titles/meta descriptions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "report_ctr_outliers"
  }
}

Input Schema

Name	Required	Description
`site`	Yes	Search Console property or domain (matched automatically).
`limit`	No
`range`	No	Preset period ending yesterday (your local calendar day). Default last_28_days. Ignored when start_date/end_date are given.
`end_date`	No	YYYY-MM-DD (use together with start_date)
`start_date`	No	YYYY-MM-DD (use together with end_date)
`min_impressions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description only needs to add context. It does clarify the metric definition (half of median CTR at same position), but does not mention the data source (Search Console), the min_impressions filtering effect, or the return shape.

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?

A single sentence that front-loads the definition and ends with the actionable takeaway. No filler, nothing redundant.

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

Completeness3/5

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

For a six-parameter reporting tool with no output schema, the description explains the core metric but leaves the impression threshold, result cap, and date-range precedence unaddressed. An agent could call it, but would be guessing about the sampling filter's effect on results.

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 67%, with 'limit' and 'min_impressions' carrying no descriptions at all, and the description does not explain either. The 'at the same position' phrase usefully clarifies how the baseline is computed, but no parameter-level meaning is added beyond the schema.

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?

Names a specific analytical output (pages whose CTR is under half the site's median CTR at the same position) and adds the actionable interpretation (title/meta candidates). It is clearly distinct from sibling reports like report_quick_wins or report_content_decay, though it does not explicitly name them.

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: the 'candidates for better titles/meta descriptions' framing signals a diagnostic SEO use case. There is no explicit when-to-use, when-not-to-use, or guidance pointing to a sibling tool for a related question.

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

All GSC Magic 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?