Skip to main content
Glama
AKzar1el

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_ranked_trends

Read-only

Get trending keywords ranked by week-over-week growth or volume for a chosen geographic region. Use this tool to obtain an ordered list of rising search topics for trend analysis.

Instructions

Return currently trending keywords ranked by week-over-week growth or volume. Use this when explicit ranked order matters; use get_top_trends for a simpler current feed and get_trends for historical series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geoNoGeographic region code (e.g. 'US').US
sortNoField to sort by.wow_pct_change
limitNoMaximum number of trends to return.
sourceNoSearch source.google search

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.22
    • changedInput schema / properties / sort / description
      Previous value: -"Field to sort by: 'wow_pct_change', 'volume'."New value: +"Field to sort by."
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "wow_pct_change",
+  "volume"
+]
    • addedInput schema / properties / source / const
      Added value: +"google search"
    • changedInput schema / properties / source / description
      Previous value: -"Search source: 'google search'."New value: +"Search source."
  2. Changed1 schema field changedv0.2.13
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  3. First observed

TDQS

A4.3/5.0
Behavior3/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 the context that results are current trending keywords and that rank order is the key feature, but does not reveal additional behavior beyond what annotations and schema already imply. No contradiction is present.

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, no filler, with the core behavior front-loaded and the sibling differentiation in the second sentence. Every word 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?

The tool has an output schema, all parameters are optional and documented, and the description provides enough context for selection and invocation. The explicit sibling guidance completes the picture for an agent deciding which trends tool to call.

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 fully documents all four parameters. The description adds minimal parameter-level meaning beyond the schema, only reinforcing that ranking can be by growth or volume, which matches the sort enum. Baseline 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 and resource: 'Return currently trending keywords ranked by week-over-week growth or volume.' It also distinguishes the tool from get_top_trends and get_trends, so an agent can tell them apart without inspecting schemas.

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 'Use this when explicit ranked order matters' and names the alternatives: get_top_trends for a simpler current feed and get_trends for historical series. This is clear routing guidance with no ambiguity.

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