Skip to main content
Glama
berlinbra

News API MCP Server

search-news

Search for news articles using a query, with optional date range, source, language, and sorting filters.

Instructions

Search for news articles on any topic

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeywords or phrases to search for in the article title and body
from_dateNoStart date for article search (YYYY-MM-DD format)
to_dateNoEnd date for article search (YYYY-MM-DD format)
sourcesNoComma-separated list of news sources to filter by (e.g., 'bbc-news,cnn')
languageNoLanguage of the articlesen
sort_byNoSort articles by relevancy, popularity, or publishedAtpublishedAt
page_sizeNoNumber of results to return per page (max 100)
pageNoPage number for pagination
Behavior2/5

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

No annotations are provided, and the description only states the purpose without disclosing behavioral details such as rate limits, authentication requirements, or full return format. The description is insufficient for an agent to understand side effects or constraints.

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 efficiently conveys the core purpose. Every word is purposeful, but it may be overly brief for the tool's complexity.

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?

With 8 parameters and no output schema, the description should explain the return format and pagination behavior. It only provides a high-level purpose, leaving the agent without key operational details.

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 each parameter is already documented in the schema. The description adds no additional meaning beyond the schema, meeting the baseline expectation for high-coverage scenarios.

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?

Description states 'Search for news articles on any topic', clearly indicating the tool's function as a search tool. The sibling tools 'get-news-sources' and 'get-top-headlines' are implicitly differentiated by their purposes, but no explicit contrast is made.

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 its siblings (e.g., top headlines, sources). An agent would have to infer usage from the tool name and parameters alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/berlinbra/news-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server