Skip to main content
Glama
purahmanian

google-trends-mcp

by purahmanian

interest_by_region

Read-only

Retrieve Google Trends interest scores broken down by region. Get the top sub-regions or countries with highest relative interest for any search term.

Instructions

Get Google Trends interest scores broken down by region (sub-country or country, depending on the geo parameter). Returns top regions with the highest relative interest for the given term.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geoNoTwo-letter country code to drill into sub-regions (e.g. "US" gives US states), or empty for worldwide country-level breakdown.
termYesThe search term to get regional interest for.
timeframeNoTrends timeframe string.today 12-m
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that it returns top regions with highest relative interest, which is useful but does not cover other behavioral traits like data freshness or pagination. No contradiction with annotations.

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 sentences, front-loaded with purpose, no extraneous information. Every part is necessary.

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

Completeness5/5

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

Given the read-only nature, rich schema descriptions, and annotations, the description adequately covers input (geo, term, timeframe) and output (top regions with relative interest). No gaps.

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 100% with parameter descriptions already present. The description adds slight nuance for geo (sub-country vs country) but largely restates schema info, so baseline 3 is appropriate.

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 clearly states the verb 'Get' and resource 'Google Trends interest scores broken down by region'. It distinguishes from sibling tools like interest_over_time (time) and compare_terms (comparison) by focusing on regional breakdown.

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?

The description explains the effect of the geo parameter (sub-country vs country), providing clear context. However, it does not explicitly state when to use this tool over alternatives or provide any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/purahmanian/google-trends-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server