GSC SEO MCP

Overview Schema Source Related Servers Discussions Admin

content_decay

Detect pages with sustained traffic decline across multiple periods, using Google Search Console data to identify content decay for focused optimization.

Instructions

Detect pages declining across multiple equal periods, not just one noisy comparison.

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": "content_decay"
  }
}

Input Schema

Name	Required	Description
`siteUrl`	No	Google Search Console property URL, e.g. sc-domain:example.com or https://www.example.com/.
`periodDays`	No
`periods`	No
`minOldestClicks`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It mentions multi-period comparison but does not disclose whether the tool is read-only, what it returns, or any side effects. Minimal transparency beyond the core function.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the key differentiator. However, for a tool with 5 parameters and no other documentation, the single sentence is too brief to be fully useful; it sacrifices completeness for conciseness.

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 the complexity (5 parameters, no output schema), the description is inadequate. It does not explain the return format, parameter constraints, or prerequisites like needing a Search Console property. Missing details required for effective use.

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

Parameters2/5

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

Schema coverage is only 20% (only siteUrl has description). The tool description adds no parameter details besides implying use of periods/periodDays. Parameters like minOldestClicks and limit are left unexplained, forcing reliance on the sparse 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?

The description states the verb 'Detect' and the resource 'pages declining across multiple equal periods', clearly distinguishing from a single noisy comparison. It gives a specific purpose, though the definition of 'declining' (clicks, impressions?) could be clearer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings like compare_periods, traffic_drop_diagnosis, or anomaly_alerts. The description implies use for multi-period decline detection, but lacks explicit context or exclusion criteria.

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