google-trends

Add Google Trends data to a question

add_trends_to_question

Fetches current Google Trends data—trending searches, interest over time, and related queries—and attaches it to a user's question so answers reflect what people are searching for now.

Instructions

Fetch the latest Google Trends data (trending searches, plus interest-over-time and related queries for any keywords given) and return the user's question with that data attached. Call this before answering any question that depends on what people are currently searching for, and then answer the enriched question.

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": {
      "question": "<question>"
    },
    "name": "add_trends_to_question"
  }
}

Input Schema

Name	Required	Description	Default
`geo`	No	Country or region code, e.g. US, GB, IN, PK, US-CA	US
`keywords`	No	Optional search terms from the question to look up in detail
`question`	Yes	The user's question, verbatim
`timeframe`	No	Google Trends time range	today 3-m
`trending_limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the unusual return contract (the original question with trend data attached) and that data is live/fresh, but says nothing about latency of an external API call, rate limits, failure behavior, or what happens when keywords is empty.

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 dense sentences with zero filler: the first states what is fetched and returned, the second states the ordering constraint. The critical instruction is front-loaded and unambiguous.

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 5-parameter tool with no output schema, the description does the important work of explaining the return value (question plus attached data) and the call ordering. Remaining gaps are operational details—three underlying queries, partial-failure handling, default behavior with no keywords—rather than anything blocking correct invocation.

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 80%, so most parameters are already documented, and the description only loosely maps 'trending searches' to trending_limit and 'interest-over-time / related queries' to keywords and timeframe. The geo parameter is never mentioned, and trending_limit has no schema description to fall back on.

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?

The description uses a specific verb and resource ('Fetch the latest Google Trends data') and enumerates the payload (trending searches, interest-over-time, related queries), which implicitly maps to the sibling tools interest_over_time, related_queries and trending_now. It never explicitly says it bundles or supersedes those siblings, so discrimination is inferential rather than stated.

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

Usage Guidelines4/5

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

It gives an explicit trigger: 'Call this before answering any question that depends on what people are currently searching for,' plus the follow-on step of answering the enriched question. There is no when-not guidance and no statement about when to call the individual sibling tools instead, which keeps it short of a 5.

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

Deploy Server