Skip to main content
Glama
GSC Opportunity MCP

GSC Opportunity MCP

by caomicc

analyze_content_decay

Identify pages losing clicks month-over-month by comparing the current window against the prior period, so you can pinpoint decaying content and prioritize refreshes.

Instructions

Pages losing clicks month-over-month (current window vs prior window).

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

Input Schema

NameRequiredDescriptionDefault
daysNo
siteNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses almost nothing: no default lookback of 28 days, no window-selection semantics, no result ordering, no volume thresholds, and no mention that zero-click or new pages may appear. The existence of an output schema relieves it of explaining return shape, but the behavioral profile of the comparison is still opaque.

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?

One short sentence with no filler and the metric front-loaded, which is good. But it reads as a truncated caption rather than a complete description, and brevity here comes from omission rather than precision.

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?

An output schema exists, so return values need not be spelled out, but the tool has three parameters at 0% coverage and default-only requiredness. The description explains only the time-window concept and leaves scope (site filtering) and result-size (limit) behavior undefined, which is not enough for a parameterized analytics tool.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate. It adds real meaning for 'days' by explaining that the value defines a current window compared against a prior window, which the bare integer does not convey. It says nothing about 'site' or 'limit', but supplying default values does help the agent call the tool correctly without further schema detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment names a specific resource ('Pages losing clicks') and a comparison method ('month-over-month, current window vs prior window'), so the analytical intent is inferable. However, it lacks a verb and never distinguishes itself from siblings like get_page_performance or get_top_opportunities, and 'content decay' is narrowed to clicks only without saying so explicitly.

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?

There is no when-to-use guidance at all: nothing says whether this is diagnostic or reporting, what precedes it, or which sibling to choose for non-click decay or single-page views. The reader must infer usage entirely from the metric named.

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