Skip to main content
Glama

BRAINIAC Technical SEO Audits

Detect keyword cannibalization

seo-technical_keyword-cannibalization-detect
Read-onlyIdempotent

Find Search Console queries where multiple pages compete on impressions and estimate lost clicks. Price $0.03 USDC. POST /api/v1/seo-technical/keyword-cannibalization-detect. An unpaid call returns the x402 payment terms and does not run.

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": {
      "rows": "<rows>"
    },
    "name": "seo-technical_keyword-cannibalization-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesrows, array. Required.
minShareNominShare, number, from any to 1. Required.
brandTermsNobrandTerms, array. Required.
minImpressionsNominImpressions, number, from 0 to any. Required.

Output Schema

NameRequiredDescriptionDefault
queriesNoqueries. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
excludedBrandNoexcludedBrand. Number.
excludedLowImpressionsNoexcludedLowImpressions. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description adds the operationally important detail an agent actually needs: the $0.03 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms without running. That is material behavior not captured in annotations; only the response shape is left to the output schema.

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?

Three short sentences, front-loaded with the analytical purpose before pricing and transport details. No filler, though the endpoint string is somewhat mechanical rather than explanatory.

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?

With an output schema present and annotations covering safety traits, the description fills the remaining gaps around cost and payment gating. It stops short of noting that 'rows' expects exported GSC query/page data and how the threshold defaults shape results, which would fully close the loop.

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 100% and includes defaults for minShare (0.1), minImpressions (100), and brandTerms, so the schema carries the parameter burden. The description adds no meaning beyond what the schema states, making the baseline 3 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?

States a specific verb and resource ('Find Search Console queries where multiple pages compete on impressions') plus the derived value ('estimate lost clicks'). This clearly distinguishes it from siblings like canonical-audit or orphan-page-detect.

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?

Implies usage by naming the input source (Search Console queries) and doing so is context, but there is no explicit when-to-use or when-not-to-use guidance, and no routing to or away from sibling diagnostics such as canonical-audit or internal-link-graph.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources