Skip to main content
Glama
ChanMeng666

Google News MCP Server

by ChanMeng666

google_news_search

Search Google News to find articles and news content with automatic topic categorization. Supports multiple languages and countries.

Instructions

Search Google News for articles and news content. Results will be automatically categorized by topic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query
glNoCountry code (e.g., us, uk)us
hlNoLanguage code (e.g., en)en
story_tokenNoStory token for full coverage of a story
topic_tokenNoTopic token for specific news topics
section_tokenNoSection token for specific sections
publication_tokenNoPublication token for specific publishers
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that results are automatically categorized by topic, adding some behavioral context, but lacks details on rate limits, authentication, or mutation implications.

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?

Two short, front-loaded sentences with no wasted words. Every sentence adds value: the first states the action, the second adds a behavioral trait.

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 7 parameters and no output schema or annotations, the description is too brief. It does not explain return format, pagination, or how to use the various tokens (story, topic, section, publication). A user would need external knowledge.

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 coverage is 100%, so the schema already documents all 7 parameters. The description does not add meaning beyond the schema, meeting the baseline for high coverage.

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 verb (Search) and resource (Google News for articles and news content), and adds that results are categorized by topic, which distinguishes it from generic web searches.

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

Usage Guidelines3/5

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

The description implies usage for searching news but provides no explicit guidance on when to use this tool versus alternatives or when not to use it. It relies on self-evident purpose.

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/ChanMeng666/server-google-news'

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