rsiddiq95/google-trends-scraper
rsiddiq95--google-trends-scraperDestructive
This tool calls the Actor "rsiddiq95/google-trends-scraper" and retrieves its output results. Actor description: Get Google Trends data: interest over time, interest by region, related queries, and Trending Now searches. Polite automatic retries, and failed lookups are never charged.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "rsiddiq95--google-trends-scraper"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| geo | No | Country or region code such as US, GB, DE or US-CA. Leave empty for worldwide. Example values: "US" | |
| category | No | Google Trends category ID to narrow results, for example 71 for Food & Drink. 0 means all categories. | |
| language | No | Interface language for labels and topic names, for example en-US or de-DE. Example values: "en-US" | en-US |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| timeRange | No | Period to analyze. Ignored when a custom time range is set. Example values: "today 12-m" | today 12-m |
| searchTerms | No | Keywords or phrases to look up on Google Trends. Each term becomes one result row. Example values: ["air fryer","standing desk"] | |
| compareTerms | No | When on, terms are compared in groups of up to 5 (like typing them together on Google Trends), so values are relative across the group. When off, each term is scaled on its own. | |
| maxConcurrency | No | How many terms to fetch in parallel. Higher is faster but more likely to be rate-limited. Example values: 2 | |
| searchProperty | No | Which Google property to measure. | |
| customTimeRange | No | Optional exact dates in the format YYYY-MM-DD YYYY-MM-DD, for example 2024-01-01 2024-12-31. | |
| trendingNowGeos | No | Country codes (for example US, GB) to fetch the current Trending Now searches for, with traffic estimates and news links. | |
| regionResolution | No | Granularity for interest by region. Auto uses Google's default for the chosen location. | |
| proxyConfiguration | No | Proxy servers used to reach Google Trends. Example values: {"useApifyProxy":true} | |
| includeRelatedQueries | No | Include top and rising related searches. Example values: true | |
| includeInterestByRegion | No | Include search interest broken down by country, state, or city. Example values: true | |
| includeInterestOverTime | No | Include the timeline of search interest (0-100). Example values: true | |
| includeLowVolumeRegions | No | Also return regions where search volume is low. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key | |
| runId | Yes | Actor run ID | |
| stats | No | Run statistics | |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED | |
| actorId | Yes | Stable Apify Actor ID from the run record | |
| summary | Yes | Past-tense summary of the run state | |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) | |
| nextStep | Yes | One primary follow-up action with identifiers interpolated | |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. | |
| actorName | No | "username/actor-name" | |
| startedAt | No | ISO timestamp when the run started | |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) | |
| statusMessage | No | Pass-through from Apify run.statusMessage | |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |