Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google Trends trending headlines

google_trends_trending_headlines_list
Read-onlyIdempotent

Fetch the ten trending Google searches and their associated news for a specified country or region to monitor current public interest and discussion.

Instructions

List the ten searches trending on Google Trends with their news. Optional inputs: geo. Returns a list.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "google_trends_trending_headlines_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoPlace: an ISO 3166-1 country code (`US`, `DE`) or a subdivision code (`US-CA`, `DE-BY`). Lowercase input is accepted and normalised to uppercase. Default: `US`.US
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds two useful behavioral facts — the result is exactly ten items and each carries associated news — which the annotations do not convey. It says nothing about rate limits, freshness/caching, or what happens when a geo has no trending data.

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?

Three short, front-loaded sentences with the core capability first. 'Returns a list' is near-redundant filler that could have carried actual return-shape information instead.

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?

There is no output schema, so the description is the only source for return values, and 'Returns a list' is thin — it does not say what fields a headline entry has or how news is attached. Combined with no sibling differentiation, this is adequate but leaves real gaps for a no-output-schema 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 geo pattern, default, and normalisation rules are already documented in structured form and the description just repeats that geo is optional. It adds no meaning for context, llm_model, or conversation_id, which are the required parameters an agent will actually be asked to fill.

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 and resource (list the ten searches trending on Google Trends) and adds the distinctive qualifier 'with their news'. It does not, however, delimit itself against the close sibling google_trends_trending_list, so an agent cannot tell what exchange-rate of value the 'news' qualifier buys.

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?

No when-to-use guidance at all — nothing says when this is preferable to google_trends_trending_list, google_news_headlines_list, or the interest/related tools. The only hint is 'Optional inputs: geo', which is a schema restatement rather than routing advice.

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