Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Related Keywords

bing_webmaster_get_related_keywords
Read-only

Find related keywords and Bing search volumes for a date window to choose the phrasing people actually use before writing or retitling a page.

Instructions

Keyword research: keywords related to one keyword, with how often each was searched on Bing over a date window, most searched first. 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. Use it to find the phrasing people actually search for before writing or retitling a page.

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_related_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum keywords to return (1-500). Defaults to 50.
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 of the window, inclusive, YYYY-MM-DD. Defaults to today (UTC). Bing's search data lags a few days and is bucketed (often weekly), so the newest days are usually empty.
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 90 days before end_date. 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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavior: strict-match vs broad_impressions semantics, default date window, Bing data lag and weekly bucketing, and result ordering. Missing are result-size or pagination notes, but the core behavioral picture is strong.

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?

Four sentences, each carrying distinct information: purpose, scope contrast, metric definition, and use case. No sentence is redundant and the scope clarification is front-loaded.

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

Completeness4/5

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

For a read-only keyword-research tool with full schema coverage, the description covers purpose, scope, metric meaning, and time-window behavior. Without an output schema it could say slightly more about the returned fields beyond impressions, but nothing essential to correct invocation is 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 coverage is 100%, so every parameter including date defaults, ISO country codes, and language tags is already documented in the schema. The description adds no parameter syntax or matching rules beyond what the schema states, so the baseline 3 applies.

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?

States a precise verb-and-resource ('keywords related to one keyword, with how often each was searched on Bing') plus the sort order. It explicitly separates itself from site-scoped siblings by noting 'This is Bing-wide search demand, not your site's traffic, so it takes no site.'

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

Usage Guidelines4/5

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

Gives a concrete when-to-use: 'find the phrasing people actually search for before writing or retitling a page.' It also implicitly rules out site-traffic questions, but it does not name a specific alternative sibling (e.g. get_keyword_stats) for that case.

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