Skip to main content
Glama
GSC Opportunity MCP

GSC Opportunity MCP

by caomicc

find_cannibalization

Detects queries where multiple pages compete and split authority, helping you consolidate content and recover ranking potential.

Instructions

Queries where two+ pages compete — authority is being split.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
siteNo
limitNo
min_impressionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Queries' hints at a read-only analysis, but it does not state the data source, whether it is safe/non-mutating, any authorization needs, or other operational constraints.

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 single sentence contains no filler and front-loads the core concept. However, its extreme brevity leaves the definition under-structured for a tool with four parameters and no annotation context.

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?

The tool has moderate complexity with four optional parameters, no annotations, and no schema descriptions. Since an output schema exists, return values need not be explained, but the description still leaves too much unstated for confident invocation.

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?

All four parameters (days, site, limit, min_impressions) have 0% schema description coverage, and the description does not mention any of them. An agent cannot tell from the description what each parameter controls, what defaults mean, or how to scope the query.

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 analytical purpose: querying where two or more pages compete for authority. The condition 'two+ pages compete' clearly maps to SEO cannibalization, though it does not explicitly differentiate itself from the sibling analysis tools.

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 explicit when-to-use guidance, no prerequisites, and no alternatives named. The description implies a cannibalization diagnostic, but leaves it to the agent to infer when this should be selected over tools like get_top_opportunities or get_page_performance.

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