Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Query Pages

bing_webmaster_get_query_pages
Read-only

Find which site pages Bing showed for a specific search query and compare their clicks, impressions, CTR, and average position over a chosen date window.

Instructions

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.

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

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 pages to return (1-1000). Defaults to 50.
queryYesThe search query exactly as bing_webmaster_get_query_stats reports it, e.g. "bing webmaster api". Bing matches it exactly, not as a substring.
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
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.3/5.0
Behavior5/5

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

Beyond the annotations, which only declare read-only and open-world behavior, the description discloses that Bing has no date parameter on this method, returns whole history, and that the tool filters, aggregates, sorts, and cuts server-side. It also explains that calling again with another window costs the same single underlying call, which is valuable operational context.

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 result is front-loaded, followed by the use case and then the important date/cost caveat. Every sentence adds useful information, and there is no filler.

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?

Although there is no output schema, the description identifies the returned page-level metrics: clicks, impressions, CTR, and position. It omits an explicit response structure and does not route to alternatives, but the rich input schema covers the parameters and the description is sufficient to call the tool correctly.

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 individual parameters are already well documented. The description adds meaningful semantic context for start_date and end_date by explaining that Bing itself has no date parameter and that this server applies the window filtering to full history, so any range Bing still holds works.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a specific resource and scope: for one search query, which pages Bing showed and how each performed. The query-to-pages direction is clear, but it does not explicitly contrast itself with the inverse sibling get_page_queries, so sibling differentiation is implied rather than stated.

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?

It gives concrete usage scenarios: find the page that ranks for a query, or find two pages competing for it. It does not say when not to use it or explicitly route the agent to alternatives.

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