Skip to main content
Glama

TrendFlow

by dev.mory

Research many trends

research_bulk
Read-only

Researches up to 10 topics in a single call, each with the same full picture as research_trend: interest over time, where it is most searched, and related queries. Each topic is looked up on its own scale, so they are not comparable to one another.

Use this when you need data across many topics — a long or rich research pass — instead of one tool call per topic. Each section is fetched independently, so a partial result is normal: any section that fails carries an error instead of data and the rest still returns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoCountry code such as "US", "GB", "TH"; a sub-region such as "US-CA"; or a US metro code such as "807". Empty string means worldwide.
topicsYes1-10 topics (terms or topic ids) to research. Each is looked up on its own scale, so they are not comparable to one another. Use this to gather data across many topics in one call instead of one tool call per topic.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds important behavioral details: each topic is looked up on its own scale (non-comparable), independent fetching per section, and normal partial failures. Does not contradict 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?

Two short paragraphs: first explains capability and structure, second gives usage guidance. No wasted words. Front-loaded with the most critical info (max 10 topics, same full picture).

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 tool has only 2 parameters (both well-documented in schema) and no output schema, the description sufficiently covers behavior, usage context, error handling, and comparability caveat. A partial result note substitutes for return format details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description reinforces parameter semantics: 'topics' must be 1-10 items, each looked up independently and not comparable across topics. Adds clarity that topics can be terms or topic IDs, which is not in the schema.

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 the tool researches up to 10 topics per call, giving the same full picture as research_trend (interest over time, regional distribution, related queries). It clearly distinguishes this bulk version from the single-topic sibling by specifying batch size and mention of 'full picture' equivalence.

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?

Explicitly advises when to use: 'when you need data across many topics — a long or rich research pass — instead of one tool call per topic.' Also explains partial results are normal, setting expectations for error handling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TrendFlow toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Each tool targets a distinct Google Trends data type—regional, temporal, related queries, trending now, topic resolution—so agents can usually tell them apart. However, research_trend overlaps with three of the get_* tools by combining their outputs, so it could be selected instead of a specific tool if the agent wants just one slice. Search topics is clearly separate.

Naming Consistency4/5

Four tools consistently use the get_verb_noun pattern (get_interest_over_time, etc.), but research_trend and search_topics deviate with different verbs while still keeping snake_case verb_noun. The pattern is readable but not perfectly uniform.

Tool Count5/5

Six tools is an appropriate number for a Google Trends server, covering the main interest endpoints plus a convenience aggregator and a topic resolver. Not too many, not too few.

Completeness4/5

The server covers the core Google Trends features: time series, regional breakdown, related queries, trending now, and topic resolution. A notable gap is the absence of a related_topics endpoint (topics related to a keyword), which complements related queries. Overall, the surface is fairly complete for typical trend research tasks.

Resources