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

bing-webmaster-mcp

by ismaelJimenez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

rank_traffic_stats

Track daily Bing impressions and clicks for your entire site to monitor search performance trends.

Instructions

Daily Bing impressions and clicks trend for the whole site.

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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior. It states what data is returned (daily impressions/clicks for the whole site), but it does not mention read-only status, output format, time range, aggregation behavior, or any operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tightly worded sentence with no filler. It is front-loaded with the core data type, though it omits a verb, making it slightly less effective than a full imperative phrase.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal for a tool with no output schema and no annotations. It does not explain the shape of the trend data, the date range covered, or how this tool should be selected over the many sibling stats tools. An agent would need additional inference or experimentation.

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 coverage is 100%, and the single siteUrl parameter is already well documented with an example and default environment variable. The description adds no additional parameter semantics, but the schema sufficiently compensates.

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 identifies the resource: a daily trend of Bing impressions and clicks for the whole site. It lacks an explicit verb like 'retrieve' or 'show', but the intent is unambiguous and the whole-site scope helps differentiate it from page-level or query-level stats.

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?

There is no guidance about when to use this tool versus siblings like query_stats, page_stats, or crawl_stats. No alternatives, exclusions, or selection criteria are mentioned, leaving the agent to infer the tool's role from its name and minimal description.

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