Skip to main content
Glama
AllNewsAPI

AllNewsAPI MCP

Official

Search News

search-news
Read-only

Search news articles by keyword, date range, category, country, or language. Apply filters for publisher, sentiment, and entity to find specific coverage from global sources.

Instructions

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.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so the safety profile is already covered. The description adds only a generic summary of parameter types, not behavioral details like pagination behavior, result limits, or paid-plan restrictions. It does not contradict the read-only hint, but adds minimal insight beyond the schema.

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 a single, focused sentence that front-loads the core action and resource, with no filler or redundancy. It is appropriately sized for the tool's purpose.

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

Completeness3/5

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

With 16 optional parameters and no output schema, the description is somewhat sparse. It conveys the basic search purpose and result type (news articles), but omits operational details like pagination, result size, and paid-plan constraints, which an agent would need to discover through the schema.

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?

The input schema covers 100% of the 16 parameters with descriptions, so the baseline is 3. The description's mention of keywords, date ranges, and filters provides a high-level grouping but no additional semantic detail beyond what the schema already documents.

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 uses the specific verb 'Search' with the resource 'news articles' and names parameter categories (keywords, date ranges, filters), clearly conveying the core function. It does not explicitly differentiate from sibling tools like headlines, so it stops short of a top score.

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 offers no guidance on when to use this tool versus the siblings headlines or usage, and provides no exclusions, prerequisites, or alternative routing. It simply states the action, leaving the agent to infer appropriate use cases.

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

Deploy Server

Other Tools