Skip to main content
Glama
zhangluka

grain-seo-mcp

by zhangluka

bing_keywords_stats

Retrieve historical keyword statistics from Bing with optional country and language filters for targeted analysis.

Instructions

Get historical stats for a keyword in Bing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesThe keyword to research
countryNoOptional country code (e.g., US)
languageNoOptional language code (e.g., en-US)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. Only states 'Get historical stats' without explaining what data is returned, time range, or any restrictions. Lacks detail on mutation or safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no extraneous words. Efficiently conveys core function.

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?

No output schema; description fails to mention what historical statistics are returned (e.g., impressions, clicks, CPC). Lacks context on time range or data granularity. Incomplete for a stats tool.

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 coverage is 100% with descriptions for all three parameters. Tool description adds no extra meaning beyond schema. Baseline score of 3 is 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?

Description clearly states verb 'Get', resource 'historical stats for a keyword', and platform 'Bing'. It distinguishes from siblings like bing_related_keywords that focus on related keywords rather than stats.

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?

No guidance on when to use this tool vs alternatives like bing_related_keywords or bing_seo_cannibalization. No mention of prerequisites or situations to avoid.

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

Deploy Server

Other Tools