A
licenseA
qualityD
maintenanceEnables fetching and parsing news articles from URLs, extracting title, text, author, and publication date.
1
2
MIT
news-article-extractor
Server Details
Extract clean article text, titles, and metadata from news URLs - ready for NLP pipelines.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- DataLeadsPRO/news-article-extractor
- GitHub Stars
- 0
- Server Listing
- news-article-extractor
TDQS
D1.7/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of selecting the wrong tool. The singular function of extracting a news article is unambiguous.
Naming Consistency3/5
The single tool name 'news_article' is a noun and does not follow a clear verb_noun pattern like 'extract_article'. There is no other tool to establish a naming convention, making consistency difficult to judge, though the name is at least somewhat descriptive.
Tool Count2/5
A single tool for a news article extractor is too few for the apparent scope. One would expect additional tools for different input types, metadata extraction, or batch processing, so the server feels under-scoped.
Completeness2/5
The tool surface is severely limited. There is no support for multiple URL handling, metadata extraction, or error management, leaving significant gaps in the news article extraction workflow.
Available Tools
1 toolnews_articleDInspect
V1 News Article
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| maxTimeout | No |
TDQS
D1.1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are providedwing, and the description contains no behavioral information at all. It does not disclose side effects, return behavior, failure modes, or any operational traits, so the agent has no basis for predicting what invoking this tool does.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The text is short but this is under-specification rather than conciseness. 'V1 News Article' carries no useful information, so it fails the requirement that every sentence earn its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having only two parameters and no output schema, the definition is still incomplete because it omits the core operation, parameter semantics, and usage context. An agent has no way to correctly select or call this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no meaning to the parameters url and maxTimeout. The schema only provides names and types, so the agent cannot infer what values are valid, what url should point to, or how maxTimeout behaves.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'V1 News Article' merely restates the tool name and adds no verb or resource. It does not say what action the tool performs, so an agent cannot know whether it fetches, parses, or searches a news article. It also fails to distinguish the tool from the siblings extract and markdown.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use news_article versus extract or markdown. The description gives no context, prerequisites, or selection criteria, leaving the agent entirely without direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
news_article
Related MCP Connectors
Convert any webpage to clean LLM-ready markdown, extraction-first, with article and news modes.
31Turn any URL into clean Markdown and structured data. Scrape, crawl, search and extract.
Clean Markdown and AI-readability scoring for any URL. Built for AI agents.
Extract and parse web pages into clean HTML, links, or Markdown. Handle dynamic, complex, or block…
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceFetches webpages and returns clean, structured Markdown with metadata (title, author, publish date, description, domain, word count).-
- AlicenseNot gradedqualityCmaintenanceEnables agents to extract article text from public URLs or HTML, verify results against acceptance contracts, and fall back across extractors while ranking future attempts using local observed outcomes.MIT
- AlicenseNot gradedqualityCmaintenanceEnables clean, LLM-ready markdown extraction from any URL with automatic anti-bot bypass.3MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.