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

bing-webmaster-mcp

by ismaelJimenez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

page_stats

Get Bing search traffic per page, including impressions and clicks, to identify which content attracts visitors.

Instructions

Top pages by Bing search traffic for the site (impressions and clicks per page).

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": "page_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

B3.4/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 reveal the core output shape (top pages with impressions and clicks), but it does not mention ranking criteria, time range, result limits, or whether the data is aggregate or dated. This is minimally adequate for a simple read-only stats tool.

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 that front-loads the key purpose and includes the most important output detail. There is no redundant wording or 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?

For a one-parameter tool with no output schema, the description states the essential result: page-level impressions and clicks from Bing search traffic. It is slightly incomplete regarding time range and ranking definition, but enough for an agent to select and invoke the tool confidently.

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 only parameter, siteUrl, has full schema description coverage, so the schema already explains it. The tool description adds no additional parameter context, but none is needed given complete schema coverage.

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 clearly states the resource ('top pages') and the metric ('Bing search traffic', 'impressions and clicks per page'), so an agent can understand what the tool returns. It does not explicitly compare against sibling tools like query_stats or rank_traffic_stats, so it falls just 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 Guidelines2/5

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

The description implies this is for page-level traffic stats, but it provides no explicit guidance on when to choose this tool over sibling tools such as query_stats or rank_traffic_stats. There are no stated exclusions, prerequisites, or alternative conditions.

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