Skip to main content
Glama

AllNewsAPI

by io.github.AllNewsAPI

Search News

search-news
Read-only

Search for news articles using various parameters including keywords, date ranges, and filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoKeywords to search for in news articles
maxNoNumber of articles to return (1-100)
langNoLanguage code(s) of the articles (e.g., 'en', 'fr')
pageNoPage number for pagination
regionNoRegion(s) to filter by (e.g., 'americas', 'europe')
sortbyNoSort results by 'publishedAt' or 'relevance' (paid plans only; omitted by default)
contentNoWhether to retrieve full article content
countryNoCountry code(s) of publication (e.g., 'us', 'gb')
endDateNoFilter articles published on or before this date (YYYY-MM-DD)
categoryNoCategory/categories to filter by (e.g., 'business', 'technology')
publisherNoFilter by specific publisher(s)
startDateNoFilter articles published on or after this date (YYYY-MM-DD)
attributesNoWhere to search for keywords: title, description, content (paid plans only; omitted by default)
ai_sentimentNoFilter by AI-analyzed sentiment (e.g., 'positive', 'negative', 'neutral')
ai_entity_nameNoFilter by entity name detected in articles
ai_entity_typeNoFilter by entity type (e.g., 'person', 'organization', 'location')

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotation readOnlyHint=true already covers the safety profile. The description adds no behavioral context beyond a generic search operation—it does not mention result format, pagination behavior, rate limits, or paid-plan restrictions. It neither contradicts the annotation nor meaningfully expands on it.

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 a single concise sentence that is front-loaded with the core action. It contains no redundant detail, though the phrase 'various parameters' is somewhat vague and could be replaced with more specific guidance.

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

Completeness2/5

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

For a tool with 16 optional parameters and no output schema, the description is too thin to be fully actionable. It does not explain what the response will contain, how results are paginated, or how this search differs from the sibling 'headlines' tool. The rich parameter schema compensates partially, but high-level behavioral context is missing.

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 description coverage is 100%, so the parameter schemas already document all 16 parameters. The description's mention of 'keywords, date ranges, and filters' loosely maps to q, startDate/endDate, and filter parameters, but it adds no new meaning beyond the schema.

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 clearly states the tool's function: 'Search for news articles' with a specific verb and resource. It does not explicitly differentiate from siblings like 'headlines' or 'usage', but the core purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'headlines'. It mentions generic filters but does not state use cases, exclusions, or situations where another tool would be more appropriate.

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

All AllNewsAPI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation5/5

Each tool serves a distinct purpose: headlines retrieves top current stories, search-news finds specific articles by query, and usage checks API limits. There is no meaningful overlap between them.

Naming Consistency3/5

Tool names are readable and lowercase but follow mixed conventions: 'headlines' is a noun, 'search-news' is a hyphenated verb-noun, and 'usage' is a noun. The pattern is not uniform but remains understandable.

Tool Count5/5

Three tools is well-scoped for a news API server focused on retrieval and quota checking. Each tool earns its place without unnecessary bloat.

Completeness4/5

The core news retrieval operations are covered: top headlines and targeted search. A source list or category metadata endpoint is missing, but agents can accomplish most tasks with the provided tools.

Resources