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

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_url_traffic_info

Retrieve traffic details for a specific page by providing site URL and page URL. Get URL traffic metrics directly from Bing Webmaster Tools.

Instructions

Get traffic details for a single page.

Args: site_url: The URL of the site url: The specific URL to get traffic info for

Returns: UrlTrafficInfo: Traffic information for the URL

Raises: BingWebmasterError: If traffic information cannot be retrieved

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>",
      "url": "<url>"
    },
    "name": "get_url_traffic_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
site_urlYes

Output Schema

NameRequiredDescriptionDefault
UrlYes
ClicksYes
IsPageYes
__typeYes
ImpressionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • removedInput schema / properties / self
      Removed value: -{
-  "title": "self",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "self",
-  "site_url",
-  "url"
-]New value: +[
+  "site_url",
+  "url"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "Clicks": {
+      "title": "Clicks",
+      "type": "integer"
+    },
+    "Impressions": {
+      "title": "Impressions",
+      "type": "integer"
+    },
+    "IsPage": {
+      "title": "Ispage",
+      "type": "boolean"
+    },
+    "Url": {
+      "title": "Url",
+      "type": "string"
+    },
+    "__type": {
+      "title": "Type",
+      "type": "string"
+    }
+  },
+  "required": [
+    "__type",
+    "Clicks",
+    "Impressions",
+    "IsPage",
+    "Url"
+  ],
+  "title": "UrlTrafficInfo",
+  "type": "object"
+}
  3. First observed

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 of behavioral disclosure. It implies a read-only operation via 'Get', but does not explicitly state that it has no side effects, does not mention authentication requirements, rate limits, or what happens when the URL is invalid or not found. The Raises clause only mentions error handling, not behavioral traits.

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

Conciseness3/5

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

The description is concise and well-structured with clear Args/Returns/Raises sections, which is good. However, the content within those sections is repetitive with the schema and provides little additional value. It is not overlong, but it does not use its brevity effectively to convey essential distinctions.

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?

Given the tool's complexity and the existence of an output schema, the description still lacks crucial context. It does not specify what traffic metrics are returned (e.g., clicks, impressions, position), whether a date range is involved, or how this differs from get_page_stats and get_rank_and_traffic_stats. Without this, an agent cannot confidently select or correctly invoke the tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. The Args section provides brief explanations ('site_url: The URL of the site', 'url: The specific URL to get traffic info for'), but these are largely tautological, restating the parameter names without adding format constraints, required patterns, or relationships. The description adds minimal meaning beyond the schema.

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 states 'Get traffic details for a single page' which is a clear verb+resource. It identifies the tool as fetching traffic information for one URL. However, it does not differentiate from many siblings like get_page_stats, get_rank_and_traffic_stats, or get_url_info, which also target single pages, so it lacks the specificity needed to distinguish it in this crowded space.

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 on when to use this tool versus its many siblings. It does not mention alternatives, exclusions, or context for selection. The description only restates the purpose without indicating scenarios where this tool is preferred, leaving an agent to guess among dozens of similar tools.

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