Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Page Queries

bing_webmaster_get_page_queries
Read-only

Retrieve the Bing search queries a specific page appeared for, with clicks, impressions, CTR, and average position over a chosen date window, filtered, sorted, and limited for analysis.

Instructions

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.

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>",
      "page": "<page>"
    },
    "name": "bing_webmaster_get_page_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe page, exactly as bing_webmaster_get_page_stats reports it (scheme and trailing slash matter) — an absolute URL, e.g. "https://example.com/pricing".
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.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the readOnlyHint/openWorldHint annotations: Bing has no date parameter, the underlying call returns the site's entire history, and the tool filters to the window, aggregates per key, sorts, and truncates. It also discloses that search data lags a few days and is bucketed (often weekly), so the newest days are usually empty, and that an ambiguous or unknown site is refused with the list of accessible ones.

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?

Three sentences, zero filler. The purpose is front-loaded, the non-obvious server-side filtering model follows, and the cost note closes it out — each sentence earns its place.

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?

With no output schema, the description carries the return-shape burden and does name the metrics returned (clicks, impressions, CTR, position) plus per-key aggregation, sorting, and truncation. What it does not spell out is whether results are always an array of per-query rows or how an empty window is represented, a minor gap for a read-only analytics tool.

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 description coverage is 100%, so all seven parameters are already documented, including defaults, the start/end date pattern and default window, and sort_by's enum semantics. The description's date-window discussion duplicates schema content rather than adding new per-parameter meaning, so the baseline of 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?

Opens with a precise verb+resource framing: '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.' The 'for one page' scoping inherently separates it from query-centric siblings like get_query_stats or get_query_pages, and it names get_page_stats as the source of the page identifier format.

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 clear context for use: one page, any window, and a cost note that re-calling with another window costs the same single call, which discourages redundant work. It also cross-references bing_webmaster_get_page_stats (page format) and bing_webmaster_list_sites (site matching). It stops short of explicit when-to-use-this-vs-alternative routing wording such as 'use get_query_pages to go the other direction.'

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