Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_feed_details

Retrieve detailed information about a specific feed for a site. Use limit and offset to paginate through feed details when results exceed the maximum rows.

Instructions

Get detailed information about a specific feed.

Args: site_url: The URL of the site feed_url: The URL of the feed

Returns: List[Feed]: Detailed feed information

Raises: BingWebmasterError: If feed details 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.
offsetNoIndex of the first row.
feed_urlYes
site_urlYes

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",
-  "site_url",
-  "feed_url"
-]New value: +[
+  "site_url",
+  "feed_url"
+]
  2. Changed1 schema field changedv1.0.0
    • 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_feed_detailsOutput",
+  "type": "object"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses pagination behavior (limit, offset, next_offset), the return type, and the error type. It does not mention side effects, but the operation is clearly a read, and the pagination detail adds meaningful transparency.

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 clear Args, Returns, Raises, and pagination sections. It is concise and avoids filler, though the Args section partially duplicates schema information.

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?

For a read-only tool with no annotations, the description covers purpose, arguments, return type, error behavior, and pagination. It lacks explicit usage guidance and details about the Feed object, but the presence of an output schema reduces the need to explain return structure.

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?

Schema coverage is only 50%, so the description must compensate for site_url and feed_url, but it only restates their names ('The URL of the site' and 'The URL of the feed'). It does add useful pagination semantics for offset via the next_offset note, but the core parameters remain under-explained.

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 a specific verb and resource: 'Get detailed information about a specific feed.' This clearly distinguishes it from list-style siblings like get_feeds by emphasizing 'specific feed,' though it does not explicitly name alternatives.

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?

The description implies it is for retrieving details about a single feed rather than listing feeds, but it gives no explicit guidance on when to prefer this tool over get_feeds or other feed-related tools. No exclusions or alternative routing are provided.

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