Extract RSS and Atom feeds from any website to monitor content updates and integrate with feed readers or content aggregation systems.
Get all RSS/Atom feeds for a site.
| Name | Required | Description | Default |
|---|---|---|---|
| site_url | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden of behavioral disclosure. It reveals the operation is read-only in a general sense and that it returns all RSS/Atom feeds, but offers no information about pagination, output format, authentication, or side effects. Minimal behavioral detail is added beyond the basic action.
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 a single concise sentence with no redundant words. It front-loads the verb and object, making the core purpose immediately clear without wasting tokens.
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?
Given the sparse schema and absence of annotations, the description is under-specified. It lacks parameter format guidance, differentiates poorly from siblings, and offers no behavioral caveats. Its low complexity prevents a score of 1, but significant gaps remain.
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?
The input schema has one required parameter, site_url, with 0% schema description coverage. The description only clarifies that site_url refers to 'a site' but does not specify expected format (e.g., URL vs. domain), validation rules, or examples. It provides only partial compensation for the schema gap.
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 states a specific verb ('Get') and resource ('all RSS/Atom feeds for a site'), making the basic operation clear. However, it does not explicitly differentiate from related siblings like get_feed_details, so it lacks the distinguishing element needed for a 5.
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 is provided on when to use this tool versus alternatives. The description does not mention contexts, exclusions, or conditions that would help an agent choose between get_feeds and sibling tools such as get_feed_details or get_fetched_urls.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.