PyScrappy

Overview Schema Source Related Servers Discussions Admin

Scrape News

scrape_news

Fetch news articles from RSS/Atom feeds, news site homepages, or individual article URLs. Returns structured data with title, URL, date, author, summary, and full text.

Instructions

Fetch news articles from an RSS/Atom feed, a news site (feed auto-discovered), or a single article, and return a list of article dicts (typically: title, url, published date, author, summary, and full text where available).

Provide exactly one of feed_url, site_url, or article_url. Fetches live content over the network at call time; results are not cached. article_url returns one article; feed_url and site_url return up to max_articles. Returns an empty list if the feed/site yields no articles or if a feed cannot be discovered or parsed.

Input Schema

TableJSON Schema

Name	Required	Description
`feed_url`	No	String, direct URL to an RSS/Atom feed. Example: "https://example.com/rss.xml". Default: None.
`site_url`	No	String, news site homepage URL whose feed is auto-discovered. Example: "https://example.com". Default: None.
`article_url`	No	String, single article URL to extract full text from. Example: "https://example.com/2026/news-story". Default: None.
`max_articles`	No	Integer, max articles to return for feed_url or site_url; ignored for article_url. Example: 20. Default: 50.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`count`	No
`errors`	No
`scraper`	No
`source_urls`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 31, 2026

changedInput schema / properties / article_url / description

Previous value: -"A single article URL to extract full text from."New value: +"String, single article URL to extract full text from. Example: \"https://example.com/2026/news-story\". Default: None."

changedInput schema / properties / feed_url / description

Previous value: -"Direct URL to an RSS/Atom feed."New value: +"String, direct URL to an RSS/Atom feed. Example: \"https://example.com/rss.xml\". Default: None."

changedInput schema / properties / max_articles / description

Previous value: -"Max articles to return from a feed (default 50)."New value: +"Integer, max articles to return for feed_url or site_url; ignored for article_url. Example: 20. Default: 50."

changedInput schema / properties / site_url / description

Previous value: -"News site URL — its feed is auto-discovered."New value: +"String, news site homepage URL whose feed is auto-discovered. Example: \"https://example.com\". Default: None."

Changed22 schema fields changedv1.3.3Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / article_url / description

Added value: +"A single article URL to extract full text from."

removedInput schema / properties / article_url / title
```
Removed value: -"Article Url"
```
addedInput schema / properties / feed_url / description
```
Added value: +"Direct URL to an RSS/Atom feed."
```
removedInput schema / properties / feed_url / title
```
Removed value: -"Feed Url"
```

addedInput schema / properties / max_articles / description

Added value: +"Max articles to return from a feed (default 50)."

removedInput schema / properties / max_articles / title
```
Removed value: -"Max Articles"
```

addedInput schema / properties / site_url / description

Added value: +"News site URL — its feed is auto-discovered."

removedInput schema / properties / site_url / title
```
Removed value: -"Site Url"
```
removedInput schema / title
```
Removed value: -"scrape_newsArguments"
```

removedOutput schema / $defs

Removed value: -{
-  "ToolError": {
-    "description": "A non-fatal problem encountered while scraping.",
-    "properties": {
-      "message": {
-        "title": "Message",
-        "type": "string"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}

removedOutput schema / properties / count / title
```
Removed value: -"Count"
```
removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
removedOutput schema / properties / errors / items / $ref
```
Removed value: -"#/$defs/ToolError"
```

addedOutput schema / properties / errors / items / description

Added value: +"A non-fatal problem encountered while scraping."

addedOutput schema / properties / errors / items / properties

Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / errors / items / required
```
Added value: +[
+  "url",
+  "message"
+]
```
addedOutput schema / properties / errors / items / type
```
Added value: +"object"
```
removedOutput schema / properties / errors / title
```
Removed value: -"Errors"
```
removedOutput schema / properties / scraper / title
```
Removed value: -"Scraper"
```
removedOutput schema / properties / source_urls / title
```
Removed value: -"Source Urls"
```
removedOutput schema / title
```
Removed value: -"ScrapeToolResult"
```

First observedv1.1.6Jul 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden. It discloses that fetches are live, results are not cached, and explains return behavior (one article vs. up to max_articles, empty list on failure). It also mentions network usage and potential non-return scenarios. This is comprehensive for a scraping tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two well-structured sentences. The first sentence states the primary purpose and output format, front-loading the core action. The second sentence provides usage constraints and behavioral details. There is no redundancy or fluff; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all essential aspects for correct invocation: input options, exclusivity constraint, return behavior, and failure handling. It accounts for network usage and caching. The presence of an output schema covers return format specifics. No critical information is missing for an agent to use this tool correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds crucial semantic value beyond the schema: it enforces mutual exclusivity of feed_url, site_url, and article_url, and clarifies that max_articles only applies to feed_url and site_url. These are not apparent from the schema alone, so the description elevates the score to 4.

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 tool fetches news articles from RSS/Atom feeds, news sites, or single articles, and returns a list of article dicts. It specifies the verb, resource, and output format, and differentiates from generic siblings like scrape_url by focusing on news content and feed auto-discovery.

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 usage instructions: 'Provide exactly one of feed_url, site_url, or article_url.' It explains the behavior of each mode and the max_articles limit. It doesn't explicitly mention when not to use this tool versus alternatives, but the purpose is unambiguous enough that an agent can select it for news-related scraping tasks.

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