Skip to main content
Glama
brdatahub-intelligence

brdatahub-intelligence

Official
by brdatahub

search_global_google_news_sentiment

Search live Google News across US, UK, BR, ES, JP, DE, and MX to track headline sentiment with publisher attribution for PR and market monitoring.

Instructions

Search live Google News across US, UK, BR, ES, JP, DE, MX with publisher attribution and headline sentiment.

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": {
      "queries": "<queries>"
    },
    "name": "search_global_google_news_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYes
timeWindowNo7d
countryEditionNoUS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful traits: the data is live, results carry publisher attribution, and each headline gets a sentiment score. It omits result caps, pagination, rate limits, and whether sentiment is per-article or aggregated, which matters for a search tool with no annotation coverage.

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?

PLACEHOLDER

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?

For a single-sentence search tool, the description conveys scope and the shape of the returned attributes, making it broadly callable. It leaves gaps on result volume and parameter behavior, but the core is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, and the description compensates only for countryEdition by naming the editions, which the enum already lists. It says nothing about how many queries to pass or whether the query array is OR-ed, and nothing about timeWindow, whose format (seen in the default '7d') and allowed values are undocumented.

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?

States a specific verb (Search) and resource (live Google News) plus the geographic scope and the two things returned: publisher attribution and headline sentiment. That is enough for an agent to distinguish it from the sibling tools, which cover cyber exploits, B2B contacts, KYB, ATS signals and Polymarket odds, though the description never explicitly routes against them.

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?

There is no when-to-use guidance, no when-not-to-use statement, and no mention of an alternative tool for non-news research. The only usage signal is implicit in the verb 'Search', so the agent must infer that this is the live-news/sentiment path.

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