Bing Webmaster Tools MCP Server

get_feeds

Retrieve all sitemap feeds for a specified site URL. Use pagination with limit and offset to fetch up to 500 feeds per request, continuing until all feeds are listed.

Instructions

Get all sitemap feeds for a site.

Args: site_url: The URL of the site

Returns: List[Feed]: List of feed information

Raises: BingWebmasterError: If feeds 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": {
+    "Feed": {
+      "properties": {
+        "Compressed": {
+          "title": "Compressed",
+          "type": "boolean"
+        },
+        "FileSize": {
+          "title": "Filesize",
+          "type": "integer"
+        },
+        "LastCrawled": {
+          "format": "date-time",
+          "title": "Lastcrawled",
+          "type": "string"
+        },
+        "Status": {
+          "title": "Status",
+          "type": "string"
+        },
+        "Submitted": {
+          "format": "date-time",
+          "title": "Submitted",
+          "type": "string"
+        },
+        "Type": {
+          "title": "Type",
+          "type": "string"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "UrlCount": {
+          "title": "Urlcount",
+          "type": "integer"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Compressed",
+        "FileSize",
+        "LastCrawled",
+        "Status",
+        "Submitted",
+        "Type",
+        "Url",
+        "UrlCount"
+      ],
+      "title": "Feed",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/Feed"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_feedsOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly explains pagination behavior (next_offset, offset), limits, and error raising, which goes beyond the schema. It does not mention read-only status, but 'get' implies it.

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 a clear purpose up front and concise Args/Returns/Raises sections. The pagination note is direct and useful, though the Args section for site_url adds little beyond the schema.

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 output schema exists, the description covers the essential call sequence, pagination, and error handling. It lacks ordering/filtering details, but these are not critical for a basic list endpoint.

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?

The schema already describes limit and offset, but site_url has no schema description. The description's mention of site_url as 'The URL of the site' is trivial and does not add meaningful constraints. With 67% schema coverage, the baseline 3 is appropriate.

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 clearly states the action ('Get all sitemap feeds') and the resource scope ('for a site'). It is distinct from sibling tools like get_feed_details or submit_feed, which have different purposes.

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

Usage Guidelines3/5

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

Provides useful context on pagination and limits, but does not explicitly state when to use this tool versus alternatives like get_feed_details for a single feed. No when-not guidance is given.

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

Deploy Server