google-trends

Trending now on Google

trending_now

Fetches current trending Google searches by country, returning approximate search volume and a related headline for each so you can answer 'what is trending right now' questions.

Instructions

Fetch the latest trending Google searches for a country, with approximate search volume and a related headline for each. Use this for 'what is trending right now' questions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trending_now"
  }
}

Input Schema

Name	Required	Description	Default
`geo`	No	Country or region code, e.g. US, GB, IN, PK, US-CA	US
`limit`	No	How many trends to return

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 of behavioral disclosure. It usefully says results are 'latest' and gives approximate volume plus a related headline, but it does not cover freshness cadence, data source limits, or other operational behavior. It is adequate but not rich.

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?

It is two tight sentences with the core action and usage guidance front-loaded. Every sentence carries useful information, with no filler or repetition.

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 and the description covers what is returned: trending searches, approximate volume, and a related headline per trend. With no output schema, that return-value information is valuable. Minor operational details are omitted, but an agent has enough to call it correctly.

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 schema already documents the geo code pattern and the limit bounds. The description reinforces the country scoping and result contents, but it does not add meaningful syntax or constraints beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: fetching the latest trending Google searches for a country. It also says what extra data comes back (search volume and a related headline). It does not explicitly differentiate itself from the sibling tools, so it falls short of a 5.

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 a clear usage trigger: 'Use this for "what is trending right now" questions.' That helps an agent know when to call it. However, it does not name alternatives or state when not to use it, so it stops short of full routing guidance.

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

Deploy Server