Skip to main content
Glama
AKzar1el

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_growth

Read-only

Calculate percentage growth for known keywords over selected timeframes to gauge momentum. Compare up to five keywords across sources like Google Search to identify rising interest.

Instructions

Estimate momentum for one or more known keywords across requested growth windows. Use this when percentage growth is the goal; use get_trends when the user needs the underlying historical time series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geoNoGeographic region code (e.g. 'US').US
sourceNoSearch source.google search
keywordYesSearch keyword(s) to analyze; comparison lists support 1-5 keywords.
percent_growthNoTimeframes to calculate growth (e.g. ['3M', '1Y']).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.22
    • changedInput schema / properties / keyword / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "items": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 5,
+    "minItems": 1,
+    "type": "array"
+  }
+]
    • changedInput schema / properties / keyword / description
      Previous value: -"Search keyword(s) to analyze."New value: +"Search keyword(s) to analyze; comparison lists support 1-5 keywords."
    • changedInput schema / properties / source / description
      Previous value: -"Search source: 'google search', 'youtube search', etc."New value: +"Search source."
    • addedInput schema / properties / source / enum
      Added value: +[
+  "google search",
+  "youtube search",
+  "news search",
+  "image search",
+  "google shopping"
+]
  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 and destructiveHint=false, so the safety profile is covered by structured data. The description adds the read-only computation framing and the 'known keywords' constraint, which is useful but not extensive. It doesn't address behaviors like handling unknown keywords or data availability, but with annotations carrying the safety burden, this is adequate.

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, zero waste. The core purpose is front-loaded and the routing guidance is delivered in a compact conditional. 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?

With an output schema present, the description need not explain return values. It covers purpose, routing, and the percentage-growth goal; the schema covers parameters and constraints (e.g., 1-5 keywords). Nothing an agent needs to invoke this correctly is missing.

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 all four parameters are already documented. The description adds only the contextual link that percent_growth is the tool's output goal, which maps to the percent_growth parameter but adds no format or syntax details beyond the schema. 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 uses a specific verb-resource pair ('Estimate momentum for one or more known keywords across requested growth windows') and explicitly differentiates from get_trends by stating the percentage-growth focus. An agent can distinguish this tool from its 15 siblings without opening 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?

Provides explicit routing: 'Use this when percentage growth is the goal; use get_trends when the user needs the underlying historical time series.' This names the alternative and the condition that selects between them, leaving nothing 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