Skip to main content
Glama
AKzar1el

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_top_trends

Read-only

Retrieve a bounded current topic feed from Google Trends RSS with related news. Set a region and limit to find top or daily trending topics.

Instructions

Return a bounded current topic discovery feed from Google Trends RSS, including related news where available. Use this for current top or daily trends; use get_ranked_trends when explicit ranking by growth or volume matters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geoNoGeographic region code (e.g. 'US').US
typeNoType of trends feed.Google Trends
limitNoMaximum number of trends to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.22
    • changedInput schema / properties / type / description
      Previous value: -"Type of trends: 'Google Trends' (realtime), 'Daily Trends' (daily)."New value: +"Type of trends feed."
    • addedInput schema / properties / type / enum
      Added value: +[
+  "Google Trends",
+  "Daily Trends"
+]
  2. Changed1 schema field changedv0.2.13
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context beyond annotations: the data source (Google Trends RSS), the feed type (current top or daily), and that related news is included where available. It does not discuss rate limits or freshness, but for a read-only RSS tool this is a minor gap.

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 with no filler. The first sentence front-loads the purpose and key qualifiers (bounded, current, Google Trends RSS, related news), and the second sentence routes to the alternative when appropriate. Every clause earns its place.

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?

With a full input schema, an output schema, and annotations covering read-only/open-world behavior, the description is largely complete. It adds source, feed type, related-news detail, and routing to get_ranked_trends. A minor gap is that it does not clarify how this relates to get_trends or get_trending_terms, but that is not essential given the existing structure and the explicit use-case guidance.

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%; all three parameters (geo, type, limit) have descriptive schema entries with defaults and an enum for type. The description adds little parameter-level meaning beyond implying the type choices, so the baseline of 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 states a specific action ('Return a bounded current topic discovery feed'), a concrete resource ('Google Trends RSS'), and explicitly names get_ranked_trends as the sibling when ranking by growth or volume matters. An agent can immediately distinguish this from related tools.

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?

It gives explicit usage guidance: 'Use this for current top or daily trends' and 'use get_ranked_trends when explicit ranking by growth or volume matters.' This provides both when-to-use and when-not-to-use with a named 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