Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_keyword_stats

Retrieve keyword statistics for a query by specifying country and language, enabling analysis of search performance and trends.

Instructions

Retrieve keyword statistics for a specific query.

Args: query: The keyword query country: The country code (i.e. gb) language: The language and country code (i.e. en-GB)

Returns: List[KeywordStats]: List of keyword statistics

Raises: BingWebmasterError: If statistics cannot be retrieved

Returns at most limit rows (default 50, max 500). When the result reports a next_offset, call again with offset=next_offset to get more rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of rows to return.
queryYes
offsetNoIndex of the first row.
countryYes
languageYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Maximum number of rows to return.",
+  "maximum": 500,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Index of the first row.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
    • removedInput schema / properties / self
      Removed value: -{
-  "title": "self",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "self",
-  "query",
-  "country",
-  "language"
-]New value: +[
+  "query",
+  "country",
+  "language"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "KeywordStats": {
+      "properties": {
+        "BroadImpressions": {
+          "title": "Broadimpressions",
+          "type": "integer"
+        },
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "Impressions": {
+          "title": "Impressions",
+          "type": "integer"
+        },
+        "Query": {
+          "title": "Query",
+          "type": "string"
+        }
+      },
+      "required": [
+        "Date",
+        "BroadImpressions",
+        "Impressions",
+        "Query"
+      ],
+      "title": "KeywordStats",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/KeywordStats"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_keyword_statsOutput",
+  "type": "object"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses pagination semantics (limit default 50, max 500, next_offset/offset loop) and the BingWebmasterError raise. It does not mention auth or rate limits, which prevents a 5.

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 well-structured with Args, Returns, Raises, and pagination note. It is concise and front-loads the core purpose, though the Args block somewhat overlaps with the input schema.

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

Completeness3/5

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

The description is usable for a simple read operation with an output schema, covering pagination and errors. However, it does not distinguish this tool from the many sibling keyword/query statistics tools, leaving the agent without enough selection context.

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 description coverage is only 40%, but the description compensates by explaining query, country (example 'gb'), and language (example 'en-GB'). Limit and offset are already documented in the schema, and the pagination note adds contextual meaning.

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?

States a clear verb and resource: 'Retrieve keyword statistics for a specific query.' However, it doesn't clarify how this differs from sibling tools like get_query_stats or get_keyword, so it stops short of full sibling 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 provides no explicit when-to-use guidance or alternatives. While 'for a specific query' implies a use case, the many sibling statistics tools make the lack of routing guidance a real gap.

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