Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

google_trends_explore_top_queries

Retrieve top related queries for Google Trends explore terms. Returns an array of top queries for specified filter combinations.

Instructions

Google Trends explore top queries. Returns the Top related queries widget for one or more Google Trends explore terms. Returns an empty queries array when Google returns no rows for the requested term/filter combination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesExplore request
Behavior2/5

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

No annotations are present, so the description is the sole source for behavioral traits. It only discloses that an empty queries array may be returned when no results exist. It does not mention side effects, authentication needs, rate limits, or other behavioral aspects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, short but includes redundancy (first sentence restates the name). It is front-loaded with the purpose but could be more concise by removing the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with a single nested object parameter and no output schema, the description is insufficient. It does not detail the request object's fields, expected format, or the response structure beyond mentioning a 'queries array'. Important context for an AI agent 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?

The schema has 100% description coverage but the description for 'request' is minimal ('Explore request'). The tool description adds that it expects 'one or more Google Trends explore terms', providing some semantic context, but does not explain the internal structure or additional fields. This is adequate but not rich.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns the Top related queries widget for one or more Google Trends explore terms. This distinguishes it from siblings like 'google_trends_explore_interest_over_time' or 'google_trends_explore_rising_queries'. The verb 'returns' and resource 'top queries' are specific.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus other Google Trends explore tools. No prerequisites, context, or comparisons with alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server