Bing Webmaster Tools MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BING_WEBMASTER_API_KEY | Yes | Your Bing Webmaster Tools API key. Generate it from Bing Webmaster Tools: Settings (gear icon) → API access → API Key → Generate. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | Lists the user's sites in Bing Webmaster Tools and whether each is verified. Call this first to get the exact siteUrl. |
| get_query_statsA | Clicks, impressions, CTR and average position per search query in Bing. Bing keeps weekly data for recent months; by default rows are summed per query over the period. |
| get_page_statsB | Clicks, impressions, CTR and average position per URL of the site in Bing (top pages). By default rows are summed per URL over the period. |
| get_pages_for_queryB | Which URLs of the site show up in Bing for a given query, with their clicks and impressions. |
| get_queries_for_pageA | Which queries bring Bing traffic to a given URL, with clicks, impressions, CTR and position. |
| get_traffic_trendA | Time series of clicks and impressions for the whole site in Bing. |
| get_query_trendB | Time series of clicks and impressions for one query in Bing. |
| get_crawl_statsC | Daily crawl data: pages crawled, crawl errors, pages in index, blocked by robots.txt, etc. |
| get_crawl_issuesB | URLs with crawl issues detected by Bingbot (error codes, malware, etc.). |
| get_url_infoB | Index information for one URL: HTTP status, discovery and last crawl dates, size, document links… |
| get_url_traffic_infoB | Clicks and impressions for one URL according to Bing's index. |
| get_sitemapsB | Submitted sitemaps and feeds: status, URLs discovered, last crawl and errors. |
| get_inbound_link_countsB | Site pages that receive external links and how many, according to Bing. Paginated. |
| get_inbound_linksA | External links pointing to one URL of the site, with anchor text. Paginated. |
| get_keyword_statsA | Historical Bing impressions for a keyword (keyword research; not tied to your site). |
| get_related_keywordsA | Keywords related to a seed keyword and their Bing impressions in a period (keyword research; not tied to your site). |
| get_url_submission_quotaB | How many URLs the site can still submit to Bing today and this month. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Most tools target a clearly distinct dimension (queries, pages, crawls, links, sitemaps, trends), and descriptions explicitly disambiguate the risky pairs like get_query_stats vs get_queries_for_page and get_page_stats vs get_pages_for_query. The only mild overlap is get_inbound_links vs get_inbound_link_counts (per-URL link detail vs per-page counts) and get_url_info vs get_url_traffic_info, but both pairs are still distinguishable from their descriptions.
Every tool follows a consistent verb_noun snake_case pattern, overwhelmingly get_* with a single list_sites. The noun phrases are descriptive and predictable across the whole set.
17 tools is slightly above the ideal range for a single-domain server, but the domain (a full webmaster analytics API) is broad and each tool maps to a distinct report or entity. None feel like filler, so it justifies its weight without being bloated.
Coverage is strong across analytics (queries, pages, trends), crawl diagnostics, sitemaps, links, and keyword research. The main gap is action-oriented operations like URL submission and sitemap submission: get_url_submission_quota hints at submission but no submit tool exists, leaving a write-side dead end.