google_trends_trending_detail
Google Trends trending term detail. Returns the Explore detail widgets for a single trending term, including interest over time, regional interest, top/rising related queries, and related topics when Google returns them.
This record as markdown: /tools/crawlora-mcp/google-trends-trending-detail.md
What google_trends_trending_detail does on Crawlora
AI agents call google_trends_trending_detail to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
request | object | Yes | Trending detail request |
Parameters from the server's own tool schema.
Why google_trends_trending_detail is rated Low
This tool retrieves and queries trend data from Google Trends. The verbs used ('Returns', 'including') indicate passive data fetching with no side effects. No data is created, modified, deleted, or used to trigger external actions. This is a straightforward Read operation with minimal security risk.
From the tool's definition Tool returns 'Explore detail widgets for a single trending term, including interest over time, regional interest, top/rising related queries, and related topics' — all data retrieval operations with no modification, deletion, or execution of external…
Attacks that exploit this kind of access
The rule that runs google_trends_trending_detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google_trends_trending_detail, this is the rule to start with:
google_trends_trending_detail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every google_trends_trending_detail call is checked against it from then on.
Questions about google_trends_trending_detail
Google Trends trending term detail. Returns the Explore detail widgets for a single trending term, including interest over time, regional interest, top/rising related queries, and related topics when Google returns them. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
google_trends_trending_detail accepts 1 parameter: request. Required: request. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for google_trends_trending_detail: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Crawlora. Nothing to install.
google_trends_trending_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the google_trends_trending_detail rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for google_trends_trending_detail. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
google_trends_trending_detail is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue