Skip to main content
Glama
GSC Opportunity MCP

GSC Opportunity MCP

by caomicc

get_top_opportunities

Rank striking-distance keywords, decaying pages, and cannibalized queries in one revenue-weighted action list to prioritize SEO fixes by estimated dollar impact.

Instructions

The headline: combine striking-distance, decay, and cannibalization into one ranked action list. Revenue-weighted with REAL per-page Raptive RPM when Raptive creds are configured in .env, else the flat CREATOR_SEO_SITE_RPM.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
siteNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a real behavioral trait beyond structure: ranking is revenue-weighted and uses real per-page Raptive RPM only when Raptive creds are configured in .env, otherwise a flat fallback RPM. It says nothing about pagination, truncation, or how ties/limits interact.

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

Conciseness4/5

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

Two tight sentences, front-loaded with the highest-value framing ("The headline") before the mechanics. The env-var-heavy second clause is dense but each part is load-bearing for understanding the ranking weights.

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

Completeness5/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 explained. Given a simple three-optional-parameter tool with a declared response shape, the description supplies the key missing context: what the ranking combines and how revenue weighting is resolved.

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 description coverage is 0% for three parameters (days, site, limit), and the description explains none of them, so the agent must infer that days controls the lookback window and limit caps the ranked list. Defaults in the schema (28, 20) mitigate this somewhat, but the description misses an easy opportunity to document the window and cap.

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?

States a concrete action and output artifact: combine striking-distance, decay, and cannibalization into one ranked action list. That distinguishes it from the sibling tools that compute each signal individually (get_striking_distance_keywords, analyze_content_decay, find_cannibalization), though it never names them explicitly.

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 headline" implies this is the preferred entry point over the individual signal tools, which is useful implicit positioning, but there is no explicit when-to-use / when-to-prefer-a-sibling statement or any prerequisite guidance beyond the Raptive credentials note.

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