Skip to main content
Glama
AKzar1el

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_categories

Read-only

Retrieve Google Trends category IDs and names for use in trend queries. Search by category name or page through results with offset and limit to get the correct cat parameter.

Instructions

Return a bounded page of Google Trends category IDs and names for use in the cat parameter of trend tools. Use query to find categories by name and offset/limit to page through broader results; do not guess category IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum categories to return in this page.
queryNoOptional case-insensitive substring to match against category names.
offsetNoZero-based offset into the filtered category list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.37
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Maximum categories to return in this page.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Zero-based offset into the filtered category list.",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "anyOf": [
+    {
+      "minLength": 1,
+      "pattern": ".*\\S.*",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional case-insensitive substring to match against category names."
+}
  2. Changed1 schema field changedv0.2.13
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  3. First observed

TDQS

A4.2/5.0
Behavior4/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. The description adds valuable context about pagination ('bounded page', 'offset/limit to page through broader results') and the warning not to guess IDs. This goes beyond the annotations without contradicting them.

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 primary purpose is front-loaded, and the usage guidance follows immediately. The warning 'do not guess category IDs' is a valuable addition that earns its place. No redundant phrasing.

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?

The tool is simple with three optional parameters and a known output schema (implied). The description covers purpose, usage, and a critical warning. For a straightforward lookup tool, nothing essential is missing. An agent can correctly invoke it with the provided 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?

Schema description coverage is 100%, so all three parameters are already documented. The description reiterates that query is for name matching and offset/limit for paging, which adds slight contextual meaning but does not introduce new semantics beyond the schema. The baseline of 3 is appropriate given full schema coverage.

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 clearly states the tool returns a bounded page of Google Trends category IDs and names, explicitly linking them to the cat parameter of trend tools. It distinguishes itself from sibling tools by focusing solely on category data, and the verb 'Return' plus resource specification is unambiguous.

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

Usage Guidelines4/5

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

The description gives explicit guidance on when to use query vs offset/limit for paging, and warns against guessing category IDs, implying this tool should be used to obtain valid IDs. It lacks explicit exclusion of alternatives, but the context of 'for use in the cat parameter' clearly defines the intended use case.

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