Skip to main content
Glama
Sign In
Google Trends MCP Server

Google Trends MCP Server

by andrewlwn77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_trends_trending

Retrieve current trending topics from Google Trends for any language and country.

Instructions

Get currently trending topics from Google Trends

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": "google_trends_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoCountry code (e.g., "US")US
languageNoLanguage code (e.g., "en")en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits, but it only states the action without details on return format, data volume, authentication needs, or rate limits. 'Get' implies a read operation, but lacks sufficient depth.

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?

The description is a single, front-loaded sentence with no unnecessary words. While concise, it could incorporate slight additional context without becoming verbose, hence a slight deduction.

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?

Given the tool's simplicity (2 optional params, 100% schema coverage, no output schema needed), the description adequately conveys the core function. However, it lacks any mention of return value characteristics (e.g., array of topics), leaving minor 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 description coverage is 100%, so the schema already documents both 'country' and 'language' parameters with examples. The description adds no extra semantics beyond what the schema provides, meeting the baseline but not exceeding it.

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 uses a specific verb 'Get' and clearly identifies the resource 'currently trending topics from Google Trends'. It effectively distinguishes from sibling tools 'google_trends_questions' and 'google_trends_status', which serve different purposes.

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?

The description provides no guidance on when to use this tool versus its siblings, nor does it mention any prerequisites or context for usage. An explicit comparison with 'google_trends_questions' or 'google_trends_status' is missing.

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