Skip to main content
Glama
AKzar1el

mcp-trendpulse

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_trends

Read-only

Retrieve historical Google Trends interest-over-time scores (0-100) for known keywords to analyze trajectory and compare performance across a specified timeframe.

Instructions

Return historical Google Trends interest-over-time points for one or more known keywords. Use this for trajectory and comparisons across a timeframe; values are normalized 0-100 interest scores, not absolute search volume. Use get_trending_terms for what is trending now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catNoGoogle Trends category ID; use 0 for all categories or a value from get_categories.
geoNoGeographic region code (e.g. 'US').US
sourceNoSearch source: 'google search', 'youtube search', 'news search', 'image search', 'google shopping'.google search
keywordYesSearch keyword(s) to analyze.
data_modeNoLegacy resolution hint used only when timeframe is omitted: 'weekly', 'daily', 'monthly'.weekly
timeframeNoExplicit TrendsPy range, for example 'today 12-m', 'today 90-d', 'all', or 'YYYY-MM-DD YYYY-MM-DD'. Overrides data_mode when supplied.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.13
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already cover read-only and non-destructive behavior, so the description adds valuable context beyond them: values are normalized 0-100 interest scores, not absolute search volume, and the tool expects 'known' keywords. This helps set accurate expectations about output semantics without contradicting the 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?

The description is two tight sentences with no filler. The core purpose is front-loaded, followed immediately by a usage directive and a named sibling alternative. Every clause earns its place.

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 rich input schema, output schema, and annotations that cover safety, the description is complete enough for an agent to select and invoke the tool correctly. It clarifies the key distinction from trending-terms tools and explains the output scale, which is the most critical contextual information.

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?

The schema already documents all six parameters at 100% coverage, so the baseline is 3. The description adds marginal context by emphasizing 'known keywords' and normalized scores, but it does not meaningfully enhance individual parameter semantics beyond what the schema already provides.

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 opens with a specific verb and resource: 'Return historical Google Trends interest-over-time points for one or more known keywords.' It clearly differentiates this tool from get_trending_terms by scoping it to historical trajectory and comparisons rather than current trends.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use this tool 'for trajectory and comparisons across a timeframe' and directs users to get_trending_terms for 'what is trending now.' This gives clear when-to-use guidance and names an alternative, leaving little to inference.

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