Skip to main content
Glama
Sign In
bing-webmaster-mcp

bing-webmaster-mcp

by ismaelJimenez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

query_stats

Retrieve top Bing search queries for your site, showing impressions, clicks, and average position over the past six months to analyze search performance.

Instructions

Top search queries on Bing for the site: impressions, clicks and average position over the trailing period the API serves (~6 months).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNoSite as registered in Bing Webmaster Tools (e.g. https://www.example.com/). Defaults to the BING_SITE_URL environment variable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It does disclose the data scope and the ~6-month trailing period, which is useful, but it omits output format, pagination, limits, and any caveats about siteUrl resolution, leaving partial transparency.

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 description is a single efficient sentence with no filler. It front-loads the main subject, then lists the relevant metrics and the time period, making it well structured and appropriately sized.

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 simple read-only stats tool with one optional parameter, the description conveys the returned metrics and the time window. Without an output schema, it explains return content at a high level, but leaves details like ordering and row count unspecified, so it is not fully complete.

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?

The schema already describes siteUrl, including its default to the BING_SITE_URL environment variable, at 100% coverage. The description adds no extra parameter meaning, so the baseline score of 3 is appropriate.

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?

The description identifies the resource ('Top search queries on Bing for the site') and the metrics (impressions, clicks, average position), making the tool's function clear. It does not explicitly contrast with siblings like page_stats or keyword_research, so it falls short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when site-level search query stats are needed, and the trailing-period qualifier adds context. However, it provides no explicit guidance on when to prefer this tool over siblings or when not to use it.

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

Deploy Server

Other Tools