Retrieve aggregate search performance metrics (clicks, impressions, CTR, position) for a site from Google or Bing, configurable for any number of days.
Get the aggregate performance metrics (clicks, impressions, CTR, position) for the last N days.
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The URL of the site | |
| days | No | Number of days to look back (default: 28) | |
| 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 provided; description mentions metrics but does not disclose if it is read-only, rate limits, or response structure. Missing details on how data is aggregated or any limitations.
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?
Single sentence, 15 words, front-loaded with action and resource. Every word adds value, no redundancy.
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?
Adequate for a simple tool with few parameters, but lacks mention of default days (28) and does not specify output format (no output schema). Could improve by clarifying aggregation scope.
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 covers all three parameters with descriptions (100% coverage). Description adds no extra meaning beyond what is in 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?
Clearly states it retrieves aggregate performance metrics (clicks, impressions, CTR, position) for the last N days, distinguishing itself from siblings like analytics_trends or analytics_query that focus on other aspects.
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?
Implied usage for aggregate summary but no explicit guidance on when to use vs. alternatives like analytics_trends or analytics_top_queries. Does not mention when not to use or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.