mcp-bing-webmaster
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BING_WEBMASTER_DEBUG | No | Set to `1` to log method names, never URLs, to stderr. | |
| BING_WEBMASTER_API_KEY | Yes | The user's Bing Webmaster API key required to authenticate with Bing Webmaster Tools. | |
| BING_WEBMASTER_API_URL | No | Base URL override, such as a proxy. Must be `https://`, or `http://` on loopback only. | |
| BING_WEBMASTER_TIMEOUT_MS | No | Per-attempt timeout in milliseconds. Valid range is 1000-300000; each call ends within 45 seconds. | 30000 |
| BING_WEBMASTER_MAX_RETRIES | No | GET retry budget for throttling, 5xx responses, and timeouts. Valid range is 0-10; POSTs are never retried. | 3 |
| BING_WEBMASTER_ALLOW_WRITES | No | Set to `1` to register the write tools and allow `bing_webmaster_request` to call non-`Get` methods. |
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 |
|---|---|
| bing_webmaster_auth_statusA | Whether an API key is configured and accepted, and which sites it reaches (count and list, with verification state). The key belongs to a user, not a site, and reaches every site that user verified — this is how to see which account it is. When unconfigured, returns the exact steps to create a key. Call this first when a tool you expected is missing. Costs one GetUserSites call (cached for 5 minutes). |
| bing_webmaster_list_sitesA | Every site the API key's user has added to Bing Webmaster Tools, in its registered form (scheme and trailing slash as Bing stores them), with whether it is verified. Unverified sites carry their verification codes. Every other tool takes one of these as |
| bing_webmaster_get_url_submission_quotaA | How many URLs the site may still submit through bing_webmaster_submit_urls: today (daily_quota) and this month (monthly_quota). The quota is per site and Bing sets it by the site's age and standing, so it differs between sites. Check it before a large submission: Bing caps a batch at what is left, so a bigger one fails. |
| bing_webmaster_get_traffic_summaryA | The site's Bing search clicks and impressions over a date window: totals plus a series, as Bing reports it (daily) or rolled up by week. Since 2023-03-24 Bing counts every vertical here — web, Copilot/chat, news, images, videos. Start here for 'how is the site doing on Bing'; then bing_webmaster_get_query_stats or bing_webmaster_get_page_stats for the breakdown. Bing has no date parameter on this method: one call returns the site's whole history, which this tool filters to the window, aggregates per key, sorts and cuts. Calling it again with another window costs the same single call. |
| bing_webmaster_get_query_statsA | The search queries the site appeared for on Bing over a date window, each with clicks, impressions, CTR and average position (impression-weighted across Bing's buckets; click_position is weighted by clicks). Bing only reports its top queries, so totals here are less than the site's — use bing_webmaster_get_traffic_summary for site totals. Bing updates this weekly. Bing has no date parameter on this method: one call returns the site's whole history, which this tool filters to the window, aggregates per key, sorts and cuts. Calling it again with another window costs the same single call. |
| bing_webmaster_get_page_statsA | The site's pages that appeared in Bing search over a date window, each with clicks, impressions, CTR and average position. Bing only reports its top pages. For the queries behind one page, use bing_webmaster_get_page_queries. Bing updates this weekly. Bing has no date parameter on this method: one call returns the site's whole history, which this tool filters to the window, aggregates per key, sorts and cuts. Calling it again with another window costs the same single call. |
| bing_webmaster_get_query_pagesA | For one search query, which of the site's pages Bing showed and how each performed (clicks, impressions, CTR, position) over a date window. Use it to find the page that ranks for a query, or two pages competing for it. Bing has no date parameter on this method: one call returns the site's whole history, which this tool filters to the window, aggregates per key, sorts and cuts. Calling it again with another window costs the same single call. |
| bing_webmaster_get_page_queriesA | For one page of the site, the search queries it appeared for on Bing and how each performed (clicks, impressions, CTR, position) over a date window. Bing has no date parameter on this method: one call returns the site's whole history, which this tool filters to the window, aggregates per key, sorts and cuts. Calling it again with another window costs the same single call. |
| bing_webmaster_get_url_infoA | Bing's URL inspection for one page: whether Bing knows it, the HTTP status it last got, when it was discovered and last crawled, document size, anchor count, and how many URLs Bing knows below it. Prefer this over a |
| bing_webmaster_get_fetched_urlA | The result of a live Bingbot fetch (requested with bing_webmaster_fetch_url, or from the dashboard's URL Inspection): status, response headers and the HTML Bingbot received. Without |
| bing_webmaster_get_crawl_statsA | How Bingbot crawled the site over a date window: pages crawled, crawl errors, responses by status class (2xx, 301, 302, 4xx, 5xx), robots.txt blocks, malware, DNS failures and timeouts, summed over the window; plus pages in the index and inbound links as first/last values (those are levels, not counters). Bing keeps about six months of daily rows and returns them all in one call; this tool filters them. |
| bing_webmaster_get_crawl_issuesA | The site's URLs with crawl problems, counted by issue type (Code4xx, Code5xx, Code301, Code302, BlockedByRobotsTxt, ImportantUrlBlockedByRobotsTxt, ContainsMalware, DnsErrors, TimeOutErrors), then the URLs themselves, most-linked first, capped by |
| bing_webmaster_list_sitemapsA | The sitemaps and feeds submitted for the site (top level only), each with its type, processing status, URL count, size and when Bing last crawled it. For the children of a sitemap index, use bing_webmaster_get_sitemap. |
| bing_webmaster_get_sitemapA | Details of one submitted sitemap. For a sitemap index, lists the child sitemaps it points to, each with status, URL count and last crawl. |
| bing_webmaster_get_link_countsA | The site's pages that have inbound links from other sites, with how many each has, one page of results at a time (page 0 first; the answer gives total_pages and next_page). For who links to one page, and with what anchor text, use bing_webmaster_get_url_links. |
| bing_webmaster_get_url_linksA | The external pages linking to one page of the site, with their anchor text, one page of results at a time (page 0 first; the answer gives total_pages and next_page). |
| bing_webmaster_get_keyword_statsA | 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. |
| bing_webmaster_get_related_keywordsA | 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. |
| bing_webmaster_requestA | Escape hatch: call any Bing Webmaster API method that has no dedicated tool, by name — e.g. GetBlockedUrls, GetCrawlSettings, GetQueryParameters, GetSiteRoles, GetSiteMoves, GetUrlTrafficInfo, GetChildrenUrlInfo, GetKeyword, GetQueryPageDetailStats. Methods: https://learn.microsoft.com/en-us/dotnet/api/microsoft.bing.webmaster.api.interfaces.iwebmasterapi. Get* methods are GET with params in |
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 19 tools
Each tool targets a distinct resource and the descriptions explicitly route between similar ones (traffic_summary vs query_stats vs page_stats, query_pages vs page_queries). The inverse pair bing_webmaster_get_query_pages / bing_webmaster_get_page_queries is the one spot where a careless agent could swap them, but the docs distinguish them clearly.
All tools carry the bing_webmaster_ prefix with a predictable verb_noun form (get_*, list_*, plus a few object-named reads). Minor deviations like auth_status and the generic request tool don't break the pattern.
19 tools is on the heavy side but justified: read-only analytics, crawl, sitemap, link and keyword domains each need several endpoints. Almost every tool earns its place, with the generic request acting as a documented overflow valve rather than filler.
Read coverage is broad, but the surface has dead ends: get_url_submission_quota references bing_webmaster_submit_urls and get_fetched_url references bing_webmaster_fetch_url, neither of which exists as a tool, and writes are globally disabled. Agents can therefore see quota but never submit URLs, and cannot trigger a fetch despite being told how to read one.