Google Trends API
Server Details
Google Trends JSON + trend summary, $0.0025/keyword; rate-limited keywords never charged.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- catalyst-labs-dev/catalyst-labs-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool targets a distinct object: aborting a run, inspecting a run, reading dataset rows, reading a key-value record, and the domain-specific trends call. The main ambiguity is structural rather than per-tool: four of five tools are generic Apify platform plumbing while the server is branded 'Google Trends API', so an agent may not realize the trends tool is self-contained (it both runs the Actor and returns results).
Four tools follow a clean kebab-case verb_noun pattern (abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record). However 'catalyst-labs--google-trends-api' breaks the convention entirely with a double-hyphen namespace/resource form and no verb, which is jarring in an otherwise predictable set.
Five tools is on the thin side, and only one of them actually serves the stated Google Trends domain; the rest are generic Actor/dataset/store accessors. It is defensible for a narrow wrapper but feels like a partial slice of a larger platform surface rather than a well-scoped server.
There is no tool to start an Actor run, yet get-actor-run and abort-actor-run explicitly reference runs 'started by any Actor-running tool' — a dead end for the core workflow. Listing operations (list datasets, list key-value store keys, list runs) and dataset metadata/schema access are also absent, leaving agents unable to discover IDs they must otherwise already know.
Available Tools
5 toolsabort-actor-runAbort Actor runADestructiveIdempotentInspect
Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.
USAGE:
Use when you need to stop a run that is taking too long or misconfigured.
USAGE EXAMPLES:
user_input: Abort run y2h7sK3Wc
user_input: Gracefully abort run y2h7sK3Wc
Inputs: runId (required), gracefully. Returns: tip, runId, stats, status, +10 more
catalyst-labs--google-trends-apicatalyst-labs/google-trends-apiBDestructiveInspect
This tool calls the Actor "catalyst-labs/google-trends-api" and retrieves its output results. Actor description: Tested Oct 25, 2026: 39/39 keywords returned Google Trends data, vs 0/40 for apify/google-trends-scraper; values match Google within 3 points. Interest over time, regions, related queries as JSON. Low-volume terms return NO_DATA, never zeros. $0.0025/keyword.
Inputs: geo, compare, category, keywords, +10 more. Returns: tip, runId, stats, status, +10 more
get-actor-runGet Actor runARead-onlyIdempotentInspect
Get detailed information about a specific Actor run.
Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.
summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").
nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").
waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.
USAGE:
Use to check the status of a run started by any Actor-running tool.
Pass waitSecs > 0 to block until terminal (or until the cap elapses).
USAGE EXAMPLES:
user_input: Show details of run y2h7sK3Wc
user_input: Wait for run y2h7sK3Wc to finish
Inputs: runId (required), waitSecs. Returns: tip, runId, stats, status, +10 more
get-dataset-itemsGet dataset itemsARead-onlyIdempotentInspect
Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields.
USAGE:
Use when you need to read data from a dataset (all items or only selected fields).
USAGE EXAMPLES:
user_input: Retrieve results from dataset abc123
user_input: Get only metadata.url and title from dataset username~my-dataset
Inputs: datasetId (required), desc, omit, clean, +4 more. Returns: items, limit, offset, summary, +5 more
get-key-value-store-recordGet key-value store recordARead-onlyIdempotentInspect
Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically.
USAGE:
Use when you need to retrieve a specific record (JSON, text, or binary) from a store.
USAGE EXAMPLES:
user_input: Get record INPUT from store abc123
user_input: Get record data.json from store username~my-store
Inputs: recordKey (required), keyValueStoreId (required). Returns: key, value, summary, contentType, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Bulk Google Trends: interest over time, regions, rising queries and plain-English trend summaries.
Google Trends: interest over time, by region and city, related and rising queries, and Trending Now in any country. Compare keywords on one scale. Runs on Apify, $1 per 1,000 keyword reports.
Google Trends data as JSON: interest over time, rising and top queries, regions, Trending Now.
Google Trends Scraper API: Interest and Trending Now
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Google Trends for search-interest signals, returning stable JSON envelopes with calibrated searches/day estimates, relative comparisons across keywords, related and rising queries, regional interest, and country-level Trending Now data. It also surfaces explicit status and error codes so agents can distinguish partial or failed results from real numbers.MIT
- AlicenseNot gradedqualityBmaintenanceEnables fetching Google Trends interest over time, regional breakdowns, and related topics and queries as JSON, with optional geography, date range, category, time zone, and Google property filters.415 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides Google Search trend data as an MCP tool, with historical series, growth percentages, and live trending searches, no scraping or rate limits.1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to fetch Google Trends data for any term, including interest over time, interest by region, and related queries and topics, all as structured JSON.162 npm58 PyPI5MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.