Skip to main content
Glama

Google News data for agents

google_news_search

Paid ($0.005). Search — Google News. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>",
      "languageCode": "<languageCode>"
    },
    "name": "google_news_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesRequired.
languageCodeYesRequired.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so well by stating the cost, the accepted payment/auth mechanisms (x402 or Authorization Bearer credits key), and that results are live JSON data. It does not mention rate limits or failure behavior, but the essential cost/authentication traits are clearly disclosed.

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 extremely compact and front-loaded, opening with the paid cost, then the action/resource, output format, and payment methods. Every clause earns its place and no words are wasted.

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

Completeness4/5

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

The tool is simple, with only two required parameters and no output schema. The description covers the resource, auth, cost, and return format (JSON), which is largely sufficient. It could have added a brief example of keyword or languageCode usage, but nothing critical is missing for selecting and invoking the tool.

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 baseline is 3 even though the schema only describes both parameters as 'Required.' The parameter names are self-explanatory, and the description adds no format or example guidance (e.g., languageCode format), but the schema already documents the parameters sufficiently.

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 uses a specific verb ('Search') and identifies the exact resource ('Google News'), making the tool's function immediately distinct from sibling tools like google_search or youtube_search_video. Even without a title, the resource name differentiates it clearly.

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 when to use the tool: whenever Google News search results are needed, and it signals a paid operation that requires credits. However, it does not explicitly contrast this tool with general web search or other search siblings, leaving some inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources