HasData Google Trends

Google Trends interest over time, by region, and related queries and topics, as JSON.

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
100%
Naming quality
30%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • LOWTool 'hasdata_google_trends_search_getTrendsData' doesn't follow camelCase/snake_casein hasdata_google_trends_search_getTrendsData
  • LOWTool 'hasdata_google_trends_search_getTrendsData' name length outside 3-30 rangein hasdata_google_trends_search_getTrendsData

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~987Tokens (tool definitions)
~9.0 KBTypical response size
Moderate attention impact (0.77% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "google-trends": {
      "command": "npx",
      "args": [
        "@hasdata/google-trends-mcp"
      ]
    }
  }
}

Runnable packages

npm@hasdata/google-trends-mcp1.0.7stdio
pypihasdata-google-trends-mcp1.0.7stdio

Remote endpoints

https://mcp.hasdata.com/api/mcp?apis=google_trendsstreamable-http
https://mcp.hasdata.com/mcp?apis=google_trendsstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢hasdata_google_trends_search_getTrendsData(q, geo, region, dataType, tz, ...)

Get Google Trends Data Pulls Google Trends data for one or more queries with geo targeting, region granularity (country/subregion/metro/city), date range, category, time zone, Google property (web, images, news, shopping, YouTube), and dataType (timeseries, geoMap, relatedTopics, relatedQueries). Returns interest-over-time series, geo-level breakdowns, and rising/top related topics/queries with relative scores. Use for keyword/content strategy, demand forecasting, seasonality analysis, topic discovery, campaign timing, and adding live-trend signals to marketing or research agents.

Input Schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Specify the search term for which you want to retrieve trends data."
    },
    "geo": {
      "type": "string",
      "description": "Specifies the location for the search. Defaults to Worldwide if not set or empty. Provide one exact documented value (3517 allowed), e.g. `AF`, `AF-BDS`."
    },
    "region": {
      "type": "string",
      "enum": [
        "country",
        "region",
        "dma",
        "city"
      ],
      "description": "Used to get more specific results when using \"Interest by region\" data type. Other data types do not accept this parameter. The default value depends on the geo location that is set.\n\nAvailable options:\n - `country`: Country\n - `region`: Subregion\n - `dma`: Metro\n - `city`: City\n\nNote: Not all region options will return results for every geo location.\n"
    },
    "dataType": {
      "type": "string",
      "enum": [
        "timeseries",
        "geoMap",
        "relatedTopics",
        "relatedQueries"
      ],
      "description": "Defines the type of search to perform.\n\nAvailable options:\n  - `timeseries`: Interest over time (default). Accepts both single and multiple queries per search.\n  - `geoMap`: Interest by region. Accepts both single and multiple queries per search.\n  - `relatedTopics`: Related topics. Accepts only single query per search.\n  - `relatedQueries`: Related queries. Accepts only single query per search.\n"
    },
    "tz": {
      "type": "number",
      "description": "Defines a time zone offset in minutes. The default value is 420 (Pacific Daylight Time (PDT): UTC-7). The valid range for this parameter is from -1439 to 1439.\n\nTo calculate the `tz` value for a specific time zone, you can use the time difference between UTC +0 and the desired time zone.\n\nExamples:\n- `420`: Pacific Daylight Time (PDT)\n- `60`: Central European Time (CET)\n- `-540`: Japan Standard Time\n"
    },
    "cat": {
      "type": "string",
      "description": "Category of the search term. The default value is 0 (\"All categories\"). Provide one exact documented value (1133 allowed), e.g. `0`, `3`."
    },
    "gprop": {
      "type": "string",
      "enum": [
        "images",
        "news",
        "froogle",
        "youtube"
      ],
      "description": "Sorts results by a specific property. The default property is Web Search (applied when the gprop parameter is not set or empty).\n\nAvailable options:\n  - `images`: Image Search\n  - `news`: News Search\n  - `froogle`: Google Shopping\n  - `youtube`: YouTube Search\n"
    },
    "date": {
      "type": "string",
      "description": "Defines a date range for the search. Available options:\n\n- `now 1-H`: Past hour\n- `now 4-H`: Past 4 hours\n- `now 1-d`: Past day\n- `now 7-d`: Past 7 days\n- `today 1-m`: Past 30 days\n- `today 3-m`: Past 90 days\n- `today 12-m`: Past 12 months\n- `today 5-y`: Past 5 years\n- `all`: 2004 - present\n\nYou can also specify a custom date range using one of the following formats:\n\n- `yyyy-mm-dd yyyy-mm-dd` - (e.g. 2021-10-15 2022-05-25) for dates from 2004 to present.\n- `yyyy-mm-ddThh yyyy-mm-ddThh` - (e.g. 2022-05-19T10 2022-05-24T22) for dates with hours within a week range. The hours will be calculated based on the tz (time zone) parameter.\n"
    }
  },
  "required": [
    "q"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools
auth requiredversion not recorded—
auth requiredversion not recorded—
auth requiredversion not recorded—