Retrieve all sitemap feeds for a specified site URL to access feed information from Bing Webmaster Tools.
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
| Name | Required | Description | Default |
|---|---|---|---|
| self | Yes | ||
| site_url | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0Output 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It only mentions returning a list and raising an error, omitting side effects, rate limits, or permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is structured with Args, Returns, Raises sections, but is excessively terse, lacking necessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With many sibling tools and moderate complexity, the description fails to provide enough context about what the feed list contains or when to use this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%. Description explains 'site_url' but completely ignores the 'self' parameter, leaving it undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'Get all' and the resource 'sitemap feeds for a site', distinguishing it from siblings like 'get_feed_details' and 'submit_feed'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives among many sibling tools, such as 'get_feed_details' or 'submit_feed', which could be confused.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zizzfizzix/mcp-server-bwt'
If you have feedback or need assistance with the MCP directory API, please join our Discord server