Skip to main content
Glama
Sign In

GSC Magic

by com.gscmagic
OverviewDiscussionsAdmin

Traffic drops and gains vs previous period

report_traffic_drops
Read-only

Compare the period with the same-length period right before it. Returns biggest click losers and gainers by page or query.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSearch Console property or domain (matched automatically).
chartNoAlso return a PNG chart of the result as an image, for clients that can display images.
limitNo
rangeNoPreset period ending yesterday (your local calendar day). Default last_28_days. Ignored when start_date/end_date are given.
end_dateNoYYYY-MM-DD (use together with start_date)
dimensionNopage
start_dateNoYYYY-MM-DD (use together with end_date)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the description's job is to add semantics, which it does: it defines the baseline as the same-length period immediately before, and discloses that results are ranked lists of losers and gainers. It does not mention pagination, limits, or that the period is chosen via range/start_date, but the core behavior is conveyed.

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 tightly written sentences, front-loaded with the comparison rule and followed by the return shape. There is no filler or restatement of the tool name.

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 7-parameter analytical tool with no output schema, the description should explain how the analyzed period is defined (preset range vs. explicit dates) and what the ranked output contains. It covers the return shape at a high level but leaves the period-selection mechanism entirely to the schema.

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 71%, so the schema already documents site, chart, range, and date formats. The description's only parameter-relevant contribution is clarifying that results are broken out 'by page or query', which maps to the dimension parameter but adds no format or default detail beyond the schema. Baseline 3 is appropriate.

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 concrete operation (compare a period against the immediately preceding same-length period) and the returned payload (biggest click losers and gainers, split by page or query). It is clearly distinct from siblings such as report_ctr_outliers or report_content_decay, though it does not explicitly contrast itself with 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?

The comparison semantics imply the use case (finding period-over-period traffic deltas), but there is no explicit statement of when to prefer this over sibling reporting tools, nor any exclusions or prerequisites such as needing a verified property.

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

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