Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Keyword Stats

bing_webmaster_get_keyword_stats
Read-only

Retrieve Bing search volume for a keyword as a weekly series with totals, enabling keyword research and demand checks over a chosen market and date range.

Instructions

Keyword research: how often a keyword was searched on Bing, as a weekly series (about six months of history) with totals over the window. This is Bing-wide search demand, not your site's traffic, so it takes no site. Impressions count searches for exactly this keyword (strict match); broad_impressions add close variants. A keyword with too little volume in the market returns no rows rather than zeros. For ideas around a keyword, use bing_webmaster_get_related_keywords.

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": {
      "query": "<query>"
    },
    "name": "bing_webmaster_get_keyword_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe keyword, e.g. "dog beds". Matched as typed; Bing does not stem it.
countryNoMarket country: a lower-case ISO 3166 code, e.g. "us", "gb", "fr". Omit for all markets. Pair it with the matching language.
end_dateNoLast day to keep, inclusive, YYYY-MM-DD. Defaults to the newest week Bing returns.
languageNoMarket language: a language-region tag, e.g. "en-US", "en-GB", "fr-FR", "nl-BE". Omit for all languages.
start_dateNoFirst day of the window, inclusive, YYYY-MM-DD. Defaults to the oldest week Bing returns. Bing returns the whole history and this server filters it, so any range Bing still holds works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only and open-world annotations, the description adds useful behavior: roughly six months of weekly history, totals over the window, strict keyword matching for impressions versus broad variants for broad_impressions, and empty results for low-volume keywords. These details materially help an agent interpret the response.

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?

The description is compact and front-loaded, starting with the core purpose and then layering in scope, matching behavior, edge cases, and the alternative. Every sentence contributes useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter read-only tool with full schema coverage but no output schema, the description supplies the missing return-shape context: weekly series, totals, strict versus broad impressions, and empty results for low volume. Nothing important for correct invocation appears to be missing.

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%, so the schema already documents query, country, language, start_date, and end_date in detail. The description reinforces that the tool takes no site and that keyword matching is strict, but it does not add much parameter-level meaning beyond the schema's own descriptions.

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?

The description gives a specific verb and resource: keyword research on how often a keyword was searched on Bing, returned as a weekly series with totals. It clearly distinguishes Bing-wide search demand from the site's own traffic and points to the related-keywords sibling for a different task.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool (Bing-wide keyword demand, no site required) and names the alternative for generating keyword ideas: bing_webmaster_get_related_keywords. It also explains the low-volume case, where no rows are returned rather than zeros.

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