Bing Webmaster Tools MCP Server

get_query_parameters

Retrieve the URL query parameters that Bing Webmaster Tools considers for URL normalization on a site. Input a site URL to get a paginated list of parameters, with offset for more rows.

Instructions

Get a list of URL normalization parameters for a site.

URL parameters are used to identify which URL parameters should be considered for URL normalization (e.g., sorting, filtering parameters that don't change the content).

Args: site_url: The URL of the site

Returns: List[QueryParameter]: List of query parameters configuration

Raises: BingWebmasterError: If parameters 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

Name	Required	Description
`limit`	No	Maximum number of rows to return.
`offset`	No	Index of the first row.
`site_url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.0Sep 26, 2026

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",
-  "site_url"
-]New value: +[
+  "site_url"
+]

Changed1 schema field changedv1.0.0Jan 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "QueryParameter": {
+      "properties": {
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "IsEnabled": {
+          "title": "Isenabled",
+          "type": "boolean"
+        },
+        "Parameter": {
+          "title": "Parameter",
+          "type": "string"
+        },
+        "Source": {
+          "title": "Source",
+          "type": "integer"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Date",
+        "IsEnabled",
+        "Parameter",
+        "Source"
+      ],
+      "title": "QueryParameter",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/QueryParameter"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_query_parametersOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the failure mode via 'Raises: BingWebmasterError' and the pagination contract with 'next_offset', which goes beyond the input schema. It does not explicitly state read-only or authentication requirements, but 'Get' plus a Returns section make the non-mutating nature clear.

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 organized with a front-loaded purpose, an Args/Returns/Raises section, and a pagination note. The middle explanation about URL parameters is slightly repetitive with the first sentence ('URL parameters' twice), but overall every major section contributes useful information without excessive fluff.

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?

Given the low-to-moderate complexity, an output schema, and schema descriptions for limit/offset, the description is largely complete: it covers return type, failure behavior, and pagination. It lacks explicit guidance about when to choose the modifying siblings instead, but for a simple read operation this is a minor gap.

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?

The schema documents limit and offset, and the description adds value by explaining that offset should be set from a returned next_offset when paginating, and by restating site_url in Args. The site_url parameter lacks a schema description, so the description at least minimally fills that gap, though it does not specify URL format requirements.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get a list of URL normalization parameters for a site.' This clearly distinguishes it from mutation siblings like add_query_parameter, remove_query_parameter, and enable_disable_query_parameter. The additional sentence about sorting/filtering parameters clarifies what the resource represents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides clear context that this is the read/retrieval operation for URL normalization parameters, and it gives practical pagination instructions for handling large result sets. It does not explicitly name the modifying sibling tools as alternatives, but the get-versus-mutate contrast is strongly implied by the description and tool names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server