Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Traffic Summary

bing_webmaster_get_traffic_summary
Read-only

Retrieve Bing search clicks and impressions for a site over a chosen date window, with totals and daily or weekly trends to assess search performance.

Instructions

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.

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_traffic_summary"
  }
}

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.
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.
intervalNonative: one point per bucket Bing reports (it documents daily updates for this method; granularity in the answer says what came back). week: summed into Monday-start weeks, easier to read over months. Defaults to native.native
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 say readOnly and openWorld, so the description carries most of the burden and does well: it discloses that Bing has no date parameter, that one call returns the whole history which the server filters, aggregates, sorts and cuts, and that data lags a few days with often-empty recent buckets. What it does not do is describe the shape of the returned totals/series fields, which matters since there is no output schema.

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?

Front-loaded with the core verb and resource, then the sibling routing, then the behavioral caveat about full-history retrieval. No filler sentences; every clause carries either scoping, routing, or caveat information.

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?

For a read-only stats tool with four fully documented parameters, the definition covers purpose, routing, aggregation modes and the data-lag caveat. The remaining gap is that with no output schema the description only vaguely characterizes the response ('totals plus a series') rather than its fields.

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, and the description earns a bump by explaining the non-obvious semantics of start_date/end_date: Bing returns full history, the server does the filtering, so any range Bing still holds is valid. The vertical-counting note (web, Copilot/chat, news, images, videos since 2023-03-24) adds meaning about what the numbers represent that the schema never states.

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?

States a specific verb and resource — 'Bing search clicks and impressions over a date window: totals plus a series' — and clarifies the two aggregation modes (native vs. week). It explicitly positions itself against bing_webmaster_get_query_stats and bing_webmaster_get_page_stats, so the agent can distinguish it from siblings without opening a schema.

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?

Gives an explicit entry point ('Start here for how is the site doing on Bing') and names the follow-on tools for breakdowns. It also preempts a likely agent behavior by noting that re-calling with another window costs the same single call, which is genuine decision guidance.

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