Skip to main content
Glama
FlorianBruniaux

gsc-mcp

by FlorianBruniaux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

seo_lost_queries

Detect search queries that lost 80%+ of their clicks versus a prior period, only including queries with at least 5 previous clicks.

Instructions

Find queries that had significant clicks previously but now have 80%+ fewer clicks.

Only queries with at least 5 clicks in the previous period are included to filter noise. Note: uses date.today() without a GSC reporting lag, so the most recent 2-3 days of the current period may include incomplete data and produce false positives.

Input Schema

NameRequiredDescriptionDefault
daysNo
siteYes
engineNogoogle

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / engine
      Added value: +{
+  "default": "google",
+  "title": "Engine",
+  "type": "string"
+}
  2. First observedv0.4.1

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well by disclosing the 80% threshold, the 5-click noise filter, and the GSC reporting-lag caveat that can cause false positives. It omits any mention of required permissions or scope constraints, but the data-reliability context is valuable.

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?

The description is three sentences, each earning its place: purpose first, filter second, caveat third. It is front-loaded, specific, and free of redundancy.

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

Completeness2/5

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

Given three parameters with zero schema descriptions and no annotations, the description should explain parameter semantics but does not. While it covers purpose and behavioral caveats adequately and an output schema exists for return values, the complete omission of parameter information leaves a significant gap.

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

Parameters1/5

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

Schema description coverage is 0% for all three parameters (site, days, engine), and the description adds no information about what any parameter means, their formats, or allowed values. For a tool with multiple undocumented parameters, the description completely fails to compensate.

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 states a specific verb and resource ('Find queries') and adds a precise condition ('80%+ fewer clicks'), making the tool's function clear. However, it does not explicitly differentiate itself from similar siblings like traffic_drops or quick_wins, so it falls 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 description implies usage for finding lost queries and includes filter criteria (at least 5 clicks) and a data caveat, but it never states when to use this tool versus alternatives or when not to use it. Guidance is therefore implied rather than explicit.

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