Skip to main content
Glama
Sign In
Bing Webmaster Tools MCP Server

Bing Webmaster Tools MCP Server

by parthguru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_page_query_stats

Retrieve search query statistics for a specific page to analyze its performance and identify keywords driving traffic.

Instructions

Get query statistics for a specific page.

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_url": "<site_url>",
      "page": "<page>"
    },
    "name": "get_page_query_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
site_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden, but it only says 'Get', implying a read operation. It does not disclose what statistics are returned, whether the tool can error, whether authentication is needed, or any response limitations.

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 efficient sentence with no filler and gets straight to the point. It loses a point only because it is so minimal that it sacrifices informative content for brevity.

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 tool has two required parameters with zero schema descriptions, no annotations, and many similar sibling tools. An output schema exists, which helps explain return values, but the description still leaves the agent without enough information to confidently select and invoke this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain either parameter. 'page' is merely echoed from the schema, and 'site_url' is not mentioned at all. The description adds no semantic value beyond the parameter names.

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 uses a clear verb and resource: 'Get query statistics' for a specific page. It is not a tautology, but it does not differentiate from the very similar sibling get_query_page_detail_stats or clarify whether 'page' refers to a URL or an internal identifier.

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 provides no guidance about when to use this tool instead of siblings like get_query_stats, get_page_stats, or get_query_page_detail_stats. It only restates a generic use case without exclusions, prerequisites, or 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