Skip to main content
Glama
Sign In
google-trends-mcp-server

google-trends-mcp-server

by dataxplore19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Google Trends: interest over time

get_interest_over_time
Read-only

Track Google Trends search interest (0–100) for one keyword over a chosen period to spot rising topics, peaks, or seasonal patterns; optionally include regional interest.

Instructions

Get Google Trends search interest (0-100) over time for one keyword, optionally with interest by region (US states, regions of a country, or countries when worldwide). Use it to see if a topic is rising, find its peak, or compare seasons. Call once per keyword: each series is scaled 0-100 on its own peak.

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": {
      "keyword": "<keyword>"
    },
    "name": "get_interest_over_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry code like US, GB, FR, DE. Empty for worldwide
keywordYesOne search term, e.g. "chatgpt" or "electric cars"
timeframeNoPeriod. Short periods give hourly points, long ones daily or weeklytoday 12-m
include_regionsNoAlso return interest by region (or by country when worldwide)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely useful behavioral detail beyond them: each series is normalized to its own peak, so magnitudes are not comparable across calls. It says nothing about failure modes for low-volume keywords, rate limits, or empty results.

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?

Three sentences, front-loaded with what it returns and followed by when to use it and the key caveat. No filler or redundant restatement of the name.

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 4-parameter read tool with full schema coverage, no output schema, and light annotations, the description covers output scale, normalization caveat, and regional expansion. The main gap is that it says nothing about empty or insufficient-data responses, which are common with Google Trends.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the geo parameter interacts with include_regions to yield US states, sub-country regions, or countries depending on scope. It also reinforces the one-keyword constraint on the required param. The timeframe granularity tradeoff is left to the schema.

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 ('Get Google Trends search interest'), the output scale (0-100), the temporal axis, and a cardinality constraint ('one keyword'). It does not explicitly distinguish itself from the only sibling, get_trending_searches, so it falls short of the 5 bar.

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?

Gives concrete use cases ('see if a topic is rising, find its peak, or compare seasons'), which tells an agent when this tool fits. It never names the alternative tool or an explicit when-not condition, so the routing guidance is incomplete.

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