Skip to main content
Glama
Sign In
Google Trends MCP Server

Google Trends MCP Server

by andrewlwn77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_trends_questions

Fetch trending questions from Google Trends filtered by language and country code.

Instructions

Get trending questions 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_questions"
  }
}

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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. No information about rate limits, data freshness, authentication, or any potential side effects is provided.

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 concise sentence, front-loading the core purpose. It is appropriately sized for a simple tool with few parameters, though it sacrifices some detail for brevity.

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

Completeness2/5

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

Given the lack of an output schema, the description should explain what the returned data looks like (e.g., list of trending questions). It fails to provide this context, leaving the agent uncertain about the response format.

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 clear descriptions for both parameters (country code and language code). The description does not add any extra meaning beyond the schema, meeting the baseline for well-described parameters.

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 clearly states 'Get trending questions from Google Trends', indicating a specific verb and resource. However, it does not fully distinguish from siblings like google_trends_trending, which might also return trending items. A slightly more precise definition would help.

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?

No guidance is provided on when to use this tool versus alternatives like google_trends_trending or google_trends_status. There are no context clues for appropriate usage scenarios.

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