Skip to main content
Glama
669,735 tools. Updated 2026-10-17 11:40

"A server for finding Google Trends data" matching MCP tools:

  • Clicks, impressions, CTR and average position from the user's own Search Console or Bing data, grouped by query, page, country, device or date. Use when: "which queries bring traffic to my site", "how did page X do last month", "impressions by country", finding queries that rank on page two, a rank check on the user's own site. Not for: a site the user does not own, use seo_get_ranked_keywords. Search volume or difficulty, use seo_get_keyword_metrics. Why a page is not indexed, use console_inspect_url. Returns: List, most clicks first, ties broken by impressions descending. rows[]: query, page, country (ISO alpha-3), device, date (the dimensions asked for; null otherwise), clicks, impressions, ctr (0 to 1), position (average, 1-based). Google data lags about two days and keeps 16 months; Bing query and page rows are the last weeks with no date range, its date rows are daily totals. Totals (sum of clicks, impressions) differ by grouping due to Google's aggregation; this is normal Google behaviour. Params: property (required), engine ("google" | bing), dimensions[] (["query"]; Bing takes one of query, page, date), start_date (default 28 days before end_date), end_date (default 3 days ago, the freshest complete day), search_type ("web"; Google), filters[] (dimension, operator, expression; Google), limit (100, cap 1000; Google serves 25,000 per query), cursor, max_credits, dry_run. Cost: 0 credits. Cached 6 hours. Example: {"property": "sc-domain:example.com", "dimensions": ["query", "page"], "start_date": "2026-08-01", "end_date": "2026-08-31"}
    ConnectorAPI key
  • Monthly Amazon search volume for up to 1,000 keywords you already have, in the order given. Use when: "how many people search Amazon for X", comparing Amazon demand with Google demand, sizing a product idea on Amazon. Not for: Google volume, use seo_get_keyword_metrics. Finding keywords, use amazon_search_keywords. Returns: List. rows[]: keyword, volume (monthly Amazon searches; null = no data). Params: keywords (required; 1 to 1000), location ("United States"), language ("en"), provider, max_credits, dry_run. Cost: 5 + 5 per 100 keywords. 10 keywords = 6 credits. Cached 7 days. Example: {"keywords": ["standing desk", "desk converter"]}
    ConnectorAPI key
  • Use for general web research (company info, news, job portals). For LinkedIn profiles use search_linkedin_people; to read one company's own site use read_company_website. General-purpose Google search — returns organic results for any query. Unlike search_google_xray (LinkedIn-only), this searches the entire web. Useful for finding job postings on portals (jobs.cz, prace.cz, profesia.sk, indeed.com), company info, news, or any other web content. Results are NOT saved to contacts — use this for research and discovery. Capped at 4 calls per minute to protect the Serper/Google budget.
    ConnectorAPI key
  • Google Trends related topics for a keyword. Returns the topics and named entities associated with a keyword in a given country, as top topics scored 0-100 relative to each other and rising topics with percentage growth, each carrying its entity type. Google Trends topic discovery for market research and content planning. [$0.03/call]. Params — keyword: the search term; geo: ISO-3166 alpha-2 country code, e.g. US, GB, DE, JP (213 countries supported); timeframe: time window. Each response reports its own bucket size in `granularity`: past_30_days and past_90_days return a daily series, past_12_months and past_5_years weekly, windows under a day hourly (2004_present|past_12_months|past_30_days|past_4_hours|past_5_years|past_7_days|past_90_days|past_day|past_hour) Example params: {'keyword': 'bitcoin', 'geo': 'US'}
    ConnectorNo auth
  • List all Google Trends category and subcategory labels you can pass to other Google Trends tools in the category field. Returns cat (array of category names, including All categories) and msg. Use this before interest-over-time or interest-by-region calls when filtering by category. Cost = 5 tokens.
    ConnectorNo auth
  • List all countries and subregions you can pass to other Google Trends tools in the country and region fields. Returns geo.countries: each country name maps to country (label) and regions (array of subregion names). Also returns msg. Use this before interest-over-time or interest-by-region calls when filtering by geography. Pair with google-trends.categories when filtering by category. Cost = 5 tokens.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Provides free Google Trends data (interest over time, term comparison, related queries, trending now, regional breakdown) to MCP-compatible AI clients without needing an API key.
    5
    188 npm
    2
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables users to retrieve current daily trending Google searches for any ISO country, including approximate traffic floors and associated news coverage.
    22 npm
    MIT

Matching MCP Connectors

  • Use this when someone asks which apps they track in AppSkyline, or an app's id is needed. Returns each app's id, name, default locale and its App Store, Mac App Store, Google Play and Microsoft Store ids, up to 100 apps. Not for finding other apps in a store.
    ConnectorNo auth
  • Use this when someone asks which apps they track in AppSkyline, or an app's id is needed. Returns each app's id, name, default locale and its App Store, Mac App Store, Google Play and Microsoft Store ids, up to 100 apps. Not for finding other apps in a store.
    ConnectorNo auth
  • The sitemaps submitted for one of the user's properties, with when they were read, how many URLs they carry and their errors. Use when: "is my sitemap picked up", "how many URLs did Google read from the sitemap", checking a submission after a site change. Not for: submitting or resubmitting one, use console_submit_sitemap. Whether one URL is indexed, use console_inspect_url. Finding pages a sitemap misses, use seo_run_technical_crawl. Returns: List. rows[]: path, type, submitted_at, last_read_at, pending, is_index, urls_submitted, urls_indexed (Google reports 0 today), warnings, errors. null = the engine does not say. Params: property (required), engine ("google" | bing), max_credits, dry_run. Cost: 0 credits. Cached 10 minutes. Example: {"property": "https://www.example.com/"}
    ConnectorAPI key
  • Search aggregate Product Hunt launch trends by category and time period; each row is a category-over-time rollup, not a product or maker record. Costs 1 credit per record returned (minimum 2), so keep `page_size` to what you need. Use datasets_producthunt_products_search or datasets_producthunt_makers_search for entity-level data.
    ConnectorNo auth
  • Fetch detailed Google Maps information for a known `place_id`. Use google_map_search to find places or google_map_place_photos and google_map_place_reviews for the full photo and review data.
    ConnectorNo auth
  • Search aggregate Product Hunt launch trends by category and time period; each row is a category-over-time rollup, not a product or maker record. Costs 1 credit per record returned (minimum 2), so keep `page_size` to what you need. Use datasets_producthunt_products_search or datasets_producthunt_makers_search for entity-level data.
    ConnectorNo auth
  • Fetch detailed Google Maps information for a known `place_id`. Use google_map_search to find places or google_map_place_photos and google_map_place_reviews for the full photo and review data.
    ConnectorNo auth
  • utilpeek: Use when an agent must tell if interest in a topic is rising or fading: Wikipedia, Hacker News and news over time. For the articles use news_search. Returns daily topic trends for 1 to 5 topics: Wikipedia page views per language, Hacker News counts, news mentions, with 7- and 28-day change, spike days, direction and share. Not Google Trends data. Public attention signals, not Google Trends or search volume. `related`: related Wikipedia topics ranked by page views; not search queries and not Google Trends data. Topic = top English Wikipedia hit (see `article.title`). Complete days to yesterday; news only for the last 14 days. Cached 6 h. Bad input is a 422 and an upstream failure a 503 or 504 (not charged). Typically 3 to 15 s (first call for a topic; cached for 6 hours). Price: USD 0.005. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/topic-trends-attention-api.html
    ConnectorNo auth
  • utilpeek: Use when an agent must tell if interest in a topic is rising or fading: Wikipedia, Hacker News and news over time. For the articles use news_search. Returns daily topic trends for 1 to 5 topics: Wikipedia page views per language, Hacker News counts, news mentions, with 7- and 28-day change, spike days, direction and share. Not Google Trends data. Public attention signals, not Google Trends or search volume. `related`: related Wikipedia topics ranked by page views; not search queries and not Google Trends data. Topic = top English Wikipedia hit (see `article.title`). Complete days to yesterday; news only for the last 14 days. Cached 6 h. Bad input is a 422 and an upstream failure a 503 or 504 (not charged). Typically 3 to 15 s (first call for a topic; cached for 6 hours). Price: USD 0.005. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/topic-trends-attention-api.html
    ConnectorNo auth
  • Get a vehicle safety profile using national complaint and recall trends. NHTSA complaints are not geocoded by state, so this returns national-level trends as context for local community safety assessments. Includes the most recent recalls and top complained-about vehicle makes. Args: state: Two-letter state abbreviation (e.g. 'CA', 'TX'). Used for crash statistics; complaint data is national.
    ConnectorNo auth
  • Get a compact overview of the user's training setup and recent activity: profile, active routine with template names, next scheduled workout, last 10 workout summaries, and strength records. Use this as a first call to orient yourself on who the user is and what they're doing. Set include_data_quality=true to also get a data_quality block (overall e1RM coverage, fragmented exercise variants, lifts that can't trend yet, stale trends) — the coverage context that tells you which numbers the data actually supports; for the full per-exercise list use list_trained_exercises. For deeper analysis, use get_training_insights. For adherence trends, use get_training_status.
    ConnectorOAuth
  • Competitive visibility from the Google Merchant Center account linked to a GSC Wizard site, for one (country, Google product category, traffic source) cell. "competitor" (default) returns one row per day per competing domain (rank, relativeVisibility, adsOrganicRatio, pageOverlapRate, higherPositionRate) plus a per-domain roll-up over the window; "top_merchant" returns one aggregate row per domain for the window (Google does not expose a date on that view); "benchmark" returns one row per day with yourDomainVisibilityTrend and categoryBenchmarkVisibilityTrend, both relative to the start of the window. relativeVisibility and adsOrganicRatio are RATIOS (200 = two hundred times as often as you); pageOverlapRate, higherPositionRate and the trends are 0-1 FRACTIONS as Google reports them (0.12 = 12%), not the 0-100 percentage ctr uses elsewhere in this server. countryCode (ISO 3166-1 alpha-2) and categoryId (Google product taxonomy id, digits) are both required because the Merchant API answers one cell per request. `reportUnavailable` (with no rows) means Google refuses this report for the Merchant Center account (eligibility); the other reports are unaffected. Returns a `notConfigured` result (not an error) when Merchant Center is not connected or no Merchant Center account is linked to the site in the GSC Wizard app. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).
    ConnectorOAuth
  • Every Google Business Profile account and location this deployment's operator credential can manage — the picker data for set_gbp_connection. Not project-scoped data (the answer does not depend on the project passed; projectId only satisfies the ownership check). Returns `{ accounts: [{ name, accountName, locations: [...] }] }`. Live Google API calls.
    ConnectorNo auth
  • Check the live Google search results for any keyword: the top 10 organic results (rank, domain, title), the People Also Ask questions, related searches, and which non-organic blocks occupy the page, so you can tell whether a query has an AI Overview or local pack slot at all. Public data, no catalog entry required. A keyword with genuinely no results returns empty arrays, which is a real finding, not an error.
    ConnectorNo auth
  • Resolves a name — a company, product, person, technology, or concept — to its Google Trends topic id (`mid`), with a `type` field that distinguishes same-name entities such as Nike the company from Nike the goddess. A topic aggregates every spelling and translation of one concept, so it measures considerably more search activity than a literal phrase: the topic for "artificial intelligence" scores 62 where the literal string scores 1. The other TrendFlow tools accept a topic id anywhere they accept a keyword.
    ConnectorNo auth