Detect pages competing for the same query in Bing to eliminate keyword cannibalization.
Detect pages competing for the same query in Bing.
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The URL of the site | |
| minImpressions | No | Minimum impressions threshold (default 50) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description should disclose behavioral traits like read-only nature, rate limits, or output format. It only states the basic purpose, omitting any operational details such as whether the tool modifies data or what the result looks like.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence of 7 words, front-loading the core purpose with no redundancy or filler. It earns its place with maximum efficiency.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without an output schema, the description should indicate what the tool returns (e.g., list of pages, scores) and how to interpret results. It does not, leaving an agent underinformed for a detection task.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with clear descriptions for both parameters ('siteUrl' and 'minImpressions'). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'detect' and the resource 'pages competing for the same query' with the scope 'Bing'. This is specific and effectively distinguishes it from siblings like 'seo_cannibalization' which likely targets other search engines.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as 'bing_seo_lost_queries' or 'bing_get_top_pages'. The description lacks context on prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.