Skip to main content
Glama
Sign In

Gouda Studios Agent Tools

by app.vercel.gouda-studios-agent-tools
OverviewDiscussionsAdmin

gouda_studios/google-trends-explorer

gouda_studios--google-trends-explorer
Destructive

Returns Google Trends interest-over-time, region interest, related queries/topics, and daily trends for keywords. Use for search-interest research.

Input Schema

NameRequiredDescriptionDefault
geoNoISO code like US, GB, DE, or US-CA. Leave empty .US
categoryNoGoogle Trends category number, 0 for all categories.
languageNoInterface language for names, e.g. en-US, de, es.en-US
maxTermsNoStop after this many terms.
propertyNoWhich Google search the trend data comes .
waitSecsNoSeconds to wait for the run to finish (0-45).
timeRangeNoHow far back to look.today 12-m
searchTermsNoKeywords or phrases. Each one is fetched separately .
trendingNowNoAdds one row per currently trending search in the chosen.
relatedTopicsNoTop and rising related topics.
relatedQueriesNoTop and rising related searches.
interestByRegionNo0-100 interest for each subregion.
interestOverTimeNoTimeline of 0-100 interest values.

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value.
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT |.
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states.
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed35 schema fields changed
    • changedInput schema / description
      Previous value: -"Fetches Google Trends data per search term: interest over time, interest by region, top and rising related queries and topics, optionally today's trending searches. Example: {\"searchTerms\":[\"ai agents\"],\"geo\":\"US\",\"timeRange\":\"today 12-m\"}. Pricing: $0.004 per search term with data."New value: +"Fetches Google Trends data per search term: interest."
    • removedInput schema / properties / category / title
      Removed value: -"Category ID"
    • changedInput schema / properties / geo / description
      Previous value: -"ISO code like US, GB, DE, or US-CA. Leave empty for worldwide."New value: +"ISO code like US, GB, DE, or US-CA. Leave empty ."
    • removedInput schema / properties / geo / title
      Removed value: -"Country or region code"
    • removedInput schema / properties / interestByRegion / title
      Removed value: -"Interest by region"
    • removedInput schema / properties / interestOverTime / title
      Removed value: -"Interest over time"
    • removedInput schema / properties / language / title
      Removed value: -"Language"
    • removedInput schema / properties / maxTerms / title
      Removed value: -"Max search terms"
    • changedInput schema / properties / property / description
      Previous value: -"Which Google search the trend data comes from."New value: +"Which Google search the trend data comes ."
    • removedInput schema / properties / property / title
      Removed value: -"Search type"
    • removedInput schema / properties / relatedQueries / title
      Removed value: -"Related queries"
    • removedInput schema / properties / relatedTopics / title
      Removed value: -"Related topics"
    • changedInput schema / properties / searchTerms / description
      Previous value: -"Keywords or phrases. Each one is fetched separately and returns one result row."New value: +"Keywords or phrases. Each one is fetched separately ."
    • removedInput schema / properties / searchTerms / prefill
      Removed value: -[
-  "bitcoin",
-  "ai agents"
-]
    • removedInput schema / properties / searchTerms / title
      Removed value: -"Search terms"
    • removedInput schema / properties / timeRange / title
      Removed value: -"Time range"
    • changedInput schema / properties / trendingNow / description
      Previous value: -"Adds one row per currently trending search in the chosen country, with traffic and news links."New value: +"Adds one row per currently trending search in the chosen."
    • removedInput schema / properties / trendingNow / title
      Removed value: -"Also get today's trending searches"
    • changedInput schema / properties / waitSecs / description
      Previous value: -"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."New value: +"Seconds to wait for the run to finish (0-45)."
    • changedOutput schema / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."
    • changedOutput schema / properties / exitCode / description
      Previous value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."
    • changedOutput schema / properties / status / description
      Previous value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."
    • changedOutput schema / properties / storages / description
      Previous value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."
    • changedOutput schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."
    • changedOutput schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / description
      Previous value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."
    • changedOutput schema / properties / storages / properties / datasets / description
      Previous value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / description
      Previous value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / description
      Previous value: -"JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema."New value: +"JSON Schema for rows in the dataset at."
    • changedOutput schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."
    • changedOutput schema / properties / storages / properties / keyValueStores / description
      Previous value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."
    • changedOutput schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."
    • changedOutput schema / properties / tip / description
      Previous value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."
    • changedOutput schema / properties / tip / properties / caveat / description
      Previous value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."
    • changedOutput schema / properties / tip / properties / message / description
      Previous value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."
  2. Added
  3. Removed
  4. Added

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, yet the description never acknowledges the tool triggers a run that consumes resources or that 'destructive' behavior is possible, nor does it explain the waitSecs polling semantics. With annotations present the bar is lower, but a destructiveHint=true scraper with no behavioral note leaves an agent unable to judge side effects or cost.

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

Conciseness4/5

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

Two short sentences, front-loaded with the returned data types before the usage hint. There is no filler or redundancy, though the second sentence is thin enough that it adds little weight.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and there are no required parameters. However, for a 13-parameter, open-world, destructive-flagged tool, the description is silent on run mechanics, cost, and how the output toggles combine, leaving moderate gaps.

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?

Schema description coverage is 100%, so all 13 parameters (geo, timeRange, property, trendingNow flags, etc.) are already documented inline. The description adds only the generic notion of 'keywords' and 'regions' without clarifying parameter interactions such as per-term fetching or the effect of the boolean toggles on output shape, so baseline 3 applies.

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 names a specific verb ('Returns') and enumerates concrete resources: interest-over-time, region interest, related queries/topics, and daily trends for keywords. That clearly distinguishes it from all listed siblings, which cover filings, awards, transcripts, and actor-run management. It loses a point only because it doesn't state the source mechanism is a Google Trends scrape/actor run.

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

Usage Guidelines3/5

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

'Use for search-interest research' implies a context but names no alternatives, prerequisites, or exclusions. Since no sibling tool overlaps with search-interest data, the lack of explicit routing is tolerable, but the guidance remains implied rather than stated.

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

All Gouda Studios Agent Tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources