Skip to main content
Glama
Sign In
creator-seo-mcp

creator-seo-mcp

by Yoshyaes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

analyze_content_decay

Identify pages with declining traffic by comparing recent and prior period performance in Google Search Console, sorted by largest percentage drop.

Instructions

Compare recent vs prior period for every page and flag declining traffic. Results are sorted worst decliners first (most negative percent change at top).

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_url": "<site_url>"
    },
    "name": "analyze_content_decay"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYesGSC property URL
min_clicksNoMinimum clicks in recent period to include
recent_daysNoLength of the recent period in days
compare_daysNoLength of the comparison period in days

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are present, so the description must disclose behavioral traits. It reveals sorting order (worst decliners first) but does not mention nondestructive behavior, authentication needs, rate limits, or output format. The description adds some context (comparison logic) but leaves gaps.

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 two sentences long with zero wasted words. It front-loads the core action and includes the key sorting behavior. Every sentence earns its place.

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

Completeness4/5

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

Given the tool has an output schema, the description does not need to explain return values. It covers the core function, sorting, and implied use case. With only one required parameter and a clear purpose, the description is nearly complete, though it could mention required data sources or assumptions (e.g., GSC access) to be fully self-contained.

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?

All 4 parameters are fully described in the schema (100% coverage), so the description adds minimal additional meaning. It mentions the comparison periods (recent vs prior) but does not elaborate on how recent_days and compare_days map to those periods. The sorting note is present but applies to output, not parameters. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool compares recent vs prior periods for every page and flags declining traffic, with results sorted by worst decliners first. This specific verb-resource combination distinguishes it from siblings like get_page_performance or get_top_opportunities.

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 use for analyzing content decay but lacks explicit guidance on when to use this tool versus alternatives like get_page_performance or find_cannibalization. No exclusions or prerequisites are mentioned, so it's adequate but not proactive.

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