Find keywords ranking in positions 8-15 to target for moving to page 1.
Find keywords ranking in positions 8-15. These are high-priority targets to push to Page 1.
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The site URL | |
| days | No | Number of days (Google only, default: 28) | |
| limit | No | Max results to return (default: 50) | |
| engine | No | The search engine (default: google) |
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 carries the full burden. It does not disclose whether the operation is read-only, requires specific permissions, or has any side effects. For a tool that likely performs a data lookup, this is a significant gap.
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 with no wasted words. It front-loads the core action and purpose immediately.
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?
The tool is simple and the description covers the main purpose, but it does not describe the output format or any limitations (e.g., which search engines or data freshness). Given that there is no output schema, the description should provide more context on what the agent will receive.
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%, so the schema already documents all parameters. The description adds no additional meaning beyond the schema; it only provides the context of rank range. Baseline 3 applies.
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 'Find keywords ranking in positions 8-15' which is a specific verb and resource, and adds context that these are high-priority targets to push to Page 1. This distinguishes the tool from sibling tools like seo_low_hanging_fruit which likely targets different rank ranges.
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?
The description implies the tool is for identifying keywords near page 1 that can be pushed further, but it does not explicitly state when to use this versus alternatives like seo_low_hanging_fruit or seo_quick_wins. The guidance is implicit but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.