Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Query Stats

bing_webmaster_get_query_stats
Read-only

Retrieves Bing search query performance for a site over a date window, including clicks, impressions, CTR, and average position; filter by text, sort, and limit results.

Instructions

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.

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": {
      "site": "<site>"
    },
    "name": "bing_webmaster_get_query_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site, e.g. "example.com" or "https://www.example.com/". Matched against the sites this API key reaches (bing_webmaster_list_sites), tolerating a missing scheme, www. or trailing slash; an ambiguous or unknown site is refused with the list of accessible ones.
limitNoMaximum queries to return (1-1000). Defaults to 50.
sort_byNoSort order, best first: clicks, impressions, ctr (highest first — noisy on keys with few impressions), or position (lowest, i.e. best, average position first). Defaults to clicks.clicks
containsNoKeep only queries containing this text (case-insensitive), e.g. "pricing".
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.
start_dateNoFirst day of the window, inclusive, YYYY-MM-DD. Defaults to 28 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.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight and does: it discloses that Bing has no date parameter, that the whole history is returned and filtered/aggregated/sorted/cut server-side, and that a second window costs no extra API call. It stops short of describing the response envelope or what an empty window returns.

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

Conciseness4/5

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

It is a single dense paragraph that front-loads the output shape and the sibling redirect before the operational caveats. Every sentence carries information, though the final note on repeat-call cost sits awkwardly at the end and the whole block is longer than typical for a list tool.

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?

With no output schema, the description must define the return shape, and it does (clicks, impressions, CTR, average position, plus weighting rules). Combined with a fully documented 6-parameter schema, an agent has everything needed to call this correctly on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds value beyond the schema by explaining how average position is impression-weighted and click_position click-weighted, and by framing the date params as a client-side filter over Bing's full history rather than an API-level range.

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 names a specific resource (search queries the site appeared for on Bing) with the exact metrics returned and a scope (a date window). It is plainly distinguishable from bing_webmaster_get_traffic_summary, which it explicitly redirects to for site totals.

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 states when to use the alternative ("use bing_webmaster_get_traffic_summary for site totals") and explains why the two disagree (Bing reports only top queries). It also sets expectations about data freshness (weekly updates, multi-day lag) and the cost of re-running with a different window.

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