Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_trends_trending

Fetch Google Trends Trending Now by country, with filters for time window, category, and status, returning ranked queries, traffic, related terms, and news.

Instructions

Google Trends trending now data. Returns Google Trends Trending Now for a country or territory (geo, default US): each trend's query, rank, search traffic, status, start and update time, related terms and news articles, with explore and share links. Filter by time window, category and status, and choose the sort order.

Input Schema

NameRequiredDescriptionDefault
hlNoGoogle Trends UI locale
tzNoTimezone offset minutes
geoNoCountry/territory location code
limitNoMaximum rows to return
statusNoTrend status filter
windowNoTrend window
sort_byNoSort mode
categoryNoTrending category id
time_rangeNoAlias for window

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.17.5
    • addedInput schema / properties / category / enum
      Added value: +[
+  0,
+  3,
+  47,
+  44,
+  22,
+  12,
+  5,
+  7,
+  71,
+  8,
+  45,
+  65,
+  11,
+  13,
+  958,
+  19,
+  16,
+  299,
+  14,
+  66,
+  29,
+  533,
+  174,
+  18,
+  20,
+  67
+]
    • addedInput schema / properties / geo / enum
      Added value: +[
+  "AF",
+  "AX",
+  "AL",
+  "DZ",
+  "AS",
+  "AD",
+  "AO",
+  "AI",
+  "AQ",
+  "AG",
+  "AR",
+  "AM",
+  "AW",
+  "AU",
+  "AT",
+  "AZ",
+  "BS",
+  "BH",
+  "BD",
+  "BB",
+  "BY",
+  "BE",
+  "BZ",
+  "BJ",
+  "BM",
+  "BT",
+  "BO",
+  "BA",
+  "BW",
+  "BV",
+  "BR",
+  "IO",
+  "VG",
+  "BN",
+  "BG",
+  "BF",
+  "BI",
+  "KH",
+  "CM",
+  "CA",
+  "CV",
+  "BQ",
+  "KY",
+  "CF",
+  "TD",
+  "CL",
+  "CN",
+  "CX",
+  "CC",
+  "CO",
+  "KM",
+  "CG",
+  "CD",
+  "CK",
+  "CR",
+  "CI",
+  "HR",
+  "CU",
+  "CW",
+  "CY",
+  "CZ",
+  "DK",
+  "DJ",
+  "DM",
+  "DO",
+  "EC",
+  "EG",
+  "SV",
+  "GQ",
+  "ER",
+  "EE",
+  "SZ",
+  "ET",
+  "FK",
+  "FO",
+  "FJ",
+  "FI",
+  "FR",
+  "GF",
+  "PF",
+  "TF",
+  "GA",
+  "GM",
+  "GE",
+  "DE",
+  "GH",
+  "GI",
+  "GR",
+  "GL",
+  "GD",
+  "GP",
+  "GU",
+  "GT",
+  "GG",
+  "GN",
+  "GW",
+  "GY",
+  "HT",
+  "HM",
+  "HN",
+  "HK",
+  "HU",
+  "IS",
+  "IN",
+  "ID",
+  "IR",
+  "IQ",
+  "IE",
+  "IM",
+  "IL",
+  "IT",
+  "JM",
+  "JP",
+  "JE",
+  "JO",
+  "KZ",
+  "KE",
+  "KI",
+  "XK",
+  "KW",
+  "KG",
+  "LA",
+  "LV",
+  "LB",
+  "LS",
+  "LR",
+  "LY",
+  "LI",
+  "LT",
+  "LU",
+  "MO",
+  "MG",
+  "MW",
+  "MY",
+  "MV",
+  "ML",
+  "MT",
+  "MH",
+  "MQ",
+  "MR",
+  "MU",
+  "YT",
+  "MX",
+  "FM",
+  "MD",
+  "MC",
+  "MN",
+  "ME",
+  "MS",
+  "MA",
+  "MZ",
+  "MM",
+  "NA",
+  "NR",
+  "NP",
+  "NL",
+  "NC",
+  "NZ",
+  "NI",
+  "NE",
+  "NG",
+  "NU",
+  "NF",
+  "KP",
+  "MK",
+  "MP",
+  "NO",
+  "OM",
+  "PK",
+  "PW",
+  "PS",
+  "PA",
+  "PG",
+  "PY",
+  "PE",
+  "PH",
+  "PN",
+  "PL",
+  "PT",
+  "PR",
+  "QA",
+  "RE",
+  "RO",
+  "RU",
+  "RW",
+  "WS",
+  "SM",
+  "ST",
+  "SA",
+  "SN",
+  "RS",
+  "SC",
+  "SL",
+  "SG",
+  "SX",
+  "SK",
+  "SI",
+  "SB",
+  "SO",
+  "ZA",
+  "GS",
+  "KR",
+  "SS",
+  "ES",
+  "LK",
+  "BL",
+  "SH",
+  "KN",
+  "LC",
+  "MF",
+  "PM",
+  "VC",
+  "SD",
+  "SR",
+  "SJ",
+  "SE",
+  "CH",
+  "SY",
+  "TW",
+  "TJ",
+  "TZ",
+  "TH",
+  "TL",
+  "TG",
+  "TK",
+  "TO",
+  "TT",
+  "TN",
+  "TR",
+  "TM",
+  "TC",
+  "TV",
+  "UM",
+  "VI",
+  "UG",
+  "UA",
+  "AE",
+  "GB",
+  "US",
+  "UY",
+  "UZ",
+  "VU",
+  "VA",
+  "VE",
+  "VN",
+  "WF",
+  "EH",
+  "YE",
+  "ZM",
+  "ZW"
+]
    • addedInput schema / properties / sort_by / enum
      Added value: +[
+  "relevance",
+  "title",
+  "recency",
+  "search_volume"
+]
    • addedInput schema / properties / status / enum
      Added value: +[
+  "all",
+  "active",
+  "ended"
+]
    • addedInput schema / properties / time_range / enum
      Added value: +[
+  "4h",
+  "24h",
+  "48h",
+  "7d"
+]
    • addedInput schema / properties / window / enum
      Added value: +[
+  "4h",
+  "24h",
+  "48h",
+  "7d"
+]
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does describe the shape of the return data (including explore/share links and related news), which is useful behavioral context absent an output schema, but it says nothing about rate limits, caching/freshness, or pagination behavior for what is implicitly a read-only endpoint.

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 sentences, front-loaded with the purpose and return content, then the filtering options. Every clause earns its place and there is no filler, though the return-field enumeration is dense.

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

Completeness4/5

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

For a 9-parameter, no-required, no-output-schema read tool, the description covers purpose, returned fields and filter dimensions adequately. The main gap is the absence of any routing guidance relative to the close sibling google_trends_trending_detail, which an agent choosing between them would benefit from.

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 the schema already documents each parameter, setting the baseline at 3. The description adds one genuinely new detail, the `geo` default of `US`, and ties window/category/status/sort to filtering intent, but it omits hl, tz, limit and time_range and adds no enum-value semantics beyond what the schema carries.

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 states a specific verb+resource ('Returns Google Trends Trending Now') and enumerates the fields returned per trend (query, rank, search traffic, status, times, related terms, news, links), so the agent knows exactly what it produces. It does not, however, distinguish itself from the sibling google_trends_trending_detail, which likely offers per-trend drill-down, so differentiation is missing.

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?

It implies usage by describing filterable dimensions (time window, category, status) and sort order, which suggests this is the list/aggregate view. But there is no explicit when-to-use versus alternatives such as google_trends_explore or google_trends_trending_detail, and no stated prerequisites or exclusions.

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

Deploy Server

Other Tools