Skip to main content
Glama
634,645 tools. Updated 2026-10-03 20:11

"How to perform a Google search" matching MCP tools:

  • Browse ALL of the user's SAVED Google Contacts for one account, one page at a time — unlike search_contacts, no query is needed, so this is how to see the whole address book (or find someone when a name search comes up empty/ambiguous). Returns each contact's name, primary email, full email list, and a `next_page_token`: pass that back as `page_token` to fetch the next page, and stop once it's null. Only ONE account per call (pagination is per-account) — pass `account` when more than one Contacts-enabled Google account is connected (call list_accounts to learn labels); it auto-resolves when only one is connected.
    ConnectorOAuth
  • 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
  • Built-in product help — ask a natural-language "how do I…" question about Fastio and get a grounded, product-aware answer (or a short clarifying question) back in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything) — read the guidance, then act with the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls to make — so prefer this over guessing endpoints or burning exploratory calls. For Q&A over YOUR uploaded files (RAG) use the `ai` tool instead — `how-to` answers questions about Fastio ITSELF. FREE and requires only an authenticated user (no org, no plan gate, no billing). Call action='describe' for the full action/param reference.
    ConnectorNo auth
  • Return how ONE page's Google Search performance changed over time. Pass start_date and end_date together as inclusive JST dates; comparison dates are not supported. Omitting both preserves the current now-minus-30-days rolling window, which may touch 31 JST dates because GSC filters by date inclusively. Explicit dates are converted to JST day boundaries for GSC rows. `granularity` defaults to day for windows up to about 35 days and week for longer windows; pass it to override. Buckets without GSC rows are omitted. Google-search only; data lags 1-2 days. site_id is optional when OAuth-authenticated. For cross-page snapshots use get_breakdown(dimension='page'); for query trends use get_keyword_performance.
    ConnectorNo auth
  • How did this exact strategy, asset and interval perform? Aggregated backtest performance for ONE specific (strategy, asset, interval) combination. Returns run_count, avg_cagr, avg_win_rate, avg_drawdown, effective_years, vs_buy_hold comparison (beats_buy_hold, cagr_delta) and an `evidence` block declaring the gate machine-readably (gate_applies_to: stats.run_count, threshold 5 runs, benchmark value, aggregation data window). For multi-strategy overview use arena_get_strategy_insights. Use this to answer 'How does strategy X perform on asset Y?'. [Free tier]
    ConnectorNo auth
  • Research keyword demand: search volume, difficulty, CPC, and intent, plus keyword ideas, Google Trends interest and related queries, and Google Ads keyword performance. Volume and difficulty come from a live keyword vendor: a workspace without vendor credits gets an explanatory error with the path forward, never fabricated numbers. Use for what to target and how much demand exists; for who ranks today use serp_competitors. Already scoped to the connected workspace and its site; call directly, no domain or site parameter is needed. Cost: metrics and suggestions bill AI credits (live vendor data at actual cost); trends, related_queries, compare and performance are FREE (Google Trends / your connected Google Ads).
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • Google Ads (Keyword Planner) monthly search volume, CPC, competition, 12-month trend and keyword difficulty (0–100, DataForSEO Labs) for up to 10 keywords in one call. Use when the user asks how often something is searched or how hard it is to rank, or to size a keyword before writing a page. Omit location_code for worldwide volume (difficulty is then computed for the US), or pass a market code for one country. Costs credits; the same keyword set re-queried within a week is free.
    ConnectorNo auth
  • Get photos for a Google Maps place. Provide place_id from search results. The identifier also accepts the business identifier form (0x...:0x...). Optional cursor, region, and language are supported. Pass cursor from a previous cursor_next to fetch the next page. Returns place metadata and a photos array. Each photo has photo_url and description when available. cursor_next appears only when a pagination cursor is available. Additional upstream fields may appear. Cost = 3 tokens.
    ConnectorNo auth
  • List supported Google Maps place type values for search filters. Returns place_types as a string array. Use a value with place_type on google-maps.search or google-maps.nearby_search. Cost = 1 token.
    ConnectorNo auth
  • Compare a local business's Google rating and review count against the top same-category rivals nearby, with the gap math done: who leads, the rating delta, the review-volume ratio, and a verdict (leading / rated_equal_or_better_but_outreviewed / trailing). Live Google Maps lookup at call time. Call this when a user wants to know how a business's reviews stack up against local competitors. Takes a few seconds. Price: $0.39 per delivered comparison.
    ConnectorNo auth
  • List sitemaps submitted for a Search Console property. Call google-search-console.list_sites to discover sites. Omit site_url to use the default property, or pass an exact site_url from that response. Returns sitemap paths plus submission, download, warning, and error details. Use an exact path from this response with get_sitemap, submit_sitemap, or delete_sitemap. Cost = 5 tokens.
    ConnectorNo auth
  • List Search Console properties for this account. Returns Vee3-managed domains plus sites added with google-search-console.add_site. Call this to discover sites, then omit site_url on later calls to use the default property, or pass an exact site_url from this response. If no properties appear, add a site with google-search-console.add_site or register a domain with domains.register. Cost = 5 tokens.
    ConnectorNo auth
  • Use this when the user asks how their site is doing IN GOOGLE SEARCH — keywords/queries they rank for, impressions, clicks from search, CTR, or average position. Backed by their own Google Search Console property (connected per site in Kleap's options), so it is the real Google data, not an estimate. Returns totals plus the top queries and top pages that produced them. Search Console lags real traffic by ~2 days — the newest days are always incomplete, say so rather than reporting a drop. If connected is false or site_selected is false, the site simply has no Search Console hooked up: call connect_search_console(app_id) — it returns a consent_url to hand the user, and that is the whole setup. Do NOT send them hunting through Kleap's settings for it. For visitors and pageviews on the site itself (all sources, not just Google), use get_analytics instead. Requires the analytics:read scope — on a 403 INSUFFICIENT_SCOPE error, tell the user to disconnect and reconnect the Kleap integration (re-authorize).
    ConnectorOAuth
  • Use this when the user asks how their site is doing IN GOOGLE SEARCH — keywords/queries they rank for, impressions, clicks from search, CTR, or average position. Backed by their own Google Search Console property (connected per site in Kleap's options), so it is the real Google data, not an estimate. Returns totals plus the top queries and top pages that produced them. Search Console lags real traffic by ~2 days — the newest days are always incomplete, say so rather than reporting a drop. If connected is false or site_selected is false, the site simply has no Search Console hooked up: call connect_search_console(app_id) — it returns a consent_url to hand the user, and that is the whole setup. Do NOT send them hunting through Kleap's settings for it. For visitors and pageviews on the site itself (all sources, not just Google), use get_analytics instead. Requires the analytics:read scope — on a 403 INSUFFICIENT_SCOPE error, tell the user to disconnect and reconnect the Kleap integration (re-authorize).
    ConnectorNo auth
  • ONE report tool for EVERY connected platform — use this for any "how did X perform" question instead of hunting for a platform-specific report tool. platform: google_ads | meta (facebook/instagram) | tiktok | linkedin | microsoft | ga4 | search_console | youtube | business_profile. account = that platform's account id (Google Ads customer_id, Meta account_id, GA4 property, Search Console site url, Business Profile location…); leave empty to use the connected/default one. days = lookback window (or give start_date/end_date as YYYY-MM-DD). level = row granularity for ad platforms (campaign | ad_group/adset | ad). breakdown = split rows by a dimension (device, day, country, age, gender, publisher_platform… for GA4/Search Console this is the dimension: channel, source, page, query…). Call describe(platform) to see exactly which levels and breakdowns that platform supports. For search_console the breakdown also takes a COMBINATION and a SORT: 'page,query' answers which page ranks for which term, and 'query by impressions' sorts by impressions instead of clicks — Search Console itself only ever returns rows by clicks, so high-impression low-click terms are invisible without it. Returns the platform's metric rows.
    ConnectorOAuth
  • Lists the website's tracked keywords (Google, in the website's default locale) with volume, difficulty, CPC, opportunity score/label, search intent, favorite flag, topic cluster label and the latest Google Search Console position, clicks, impressions and top ranking page. Pages of 50; sort by opportunity (default), volume, position (best first, unranked last) or recent. Use search to filter by keyword text and favorites_only to keep starred keywords. Positions are null when Google Search Console is not connected. Returns keyword_id values used by every other keyword tool. Pass website_id when the account has several websites (see get_account).
    ConnectorOAuth
  • Returns one keyword with its metrics, the last 90 days of Google Search Console position history (per day and country), the scheduled and generated articles targeting it, and up to 20 sibling keywords of the same topic cluster. Position history is empty when Google Search Console is not connected. Pass website_id when the account has several websites (see get_account).
    ConnectorOAuth
  • Run the Time Machine simulation to see how your idea would perform in different eras (past, present and future scenarios), returning a session ID for the async result. This spends credits and starts a background job. Not read-only; pass an ideaId you own and confirm your credit balance first.
    ConnectorNo auth
  • Set or clear the Final URL Suffix on a wizard campaign's search channel (Google Ads or Microsoft Ads). The suffix is appended to every final URL the platform serves — typically UTM parameters for tracking (utm_source, utm_medium, utm_campaign, ...). Matches the platform UI's "Final URL Suffix" input under the Google Ads / Microsoft Ads channel's Advanced Settings section. KEYWORDS: final url suffix, final-url-suffix, url suffix, suffix, utm, utm parameters, utm source, utm medium, utm campaign, tracking, tracking template, url tracking, tracking parameters, google ads, google, microsoft ads, microsoft, bing, search channel, search campaign, campaign settings, advanced settings WHEN TO USE: - Add or change UTM / tracking parameters on Google Ads or Microsoft Ads final URLs - Clear an existing suffix (pass empty string "") REQUIREMENTS: - The campaign MUST already have the target channel enabled (via create_campaign / add_and_edit_campaign_elements with a `google` and/or `microsoft` block). - Final URL Suffix is search-channel-only. LinkedIn / Meta / Reddit do NOT support it and the tool will reject other channel types. PARAMETERS: - campaign_id (required): the wizard campaign ID. - channel (required): "GOOGLE_ADS" or "MICROSOFT_ADS". - final_url_suffix (required): the suffix string. Max 2048 chars. Format: key=value pairs separated by `&`. Allowed characters: A–Z a–z 0–9 . _ ~ = & { } - or %XX percent-encoded. Spaces and [ ] ( ) # ? must be percent-encoded. Pass empty string "" to clear. EXAMPLES: Set UTMs on a Google Ads channel: set_search_channel_final_url_suffix({ "campaign_id": 177214, "channel": "GOOGLE_ADS", "final_url_suffix": "utm_source=metadata&utm_medium=cpc&utm_campaign={campaignid}" }) Clear the suffix on a Microsoft Ads channel: set_search_channel_final_url_suffix({ "campaign_id": 177214, "channel": "MICROSOFT_ADS", "final_url_suffix": "" }) RESPONSE: {success, campaign_id, channel_id, channel, applied:{final_url_suffix}, errors?} INTEGRATION WITH OTHER TOOLS: - Use search_campaigns_by_names / get_campaign_by_wizard_id to find the campaign. - Google Ads / Microsoft Ads channels are enabled by create_campaign or add_and_edit_campaign_elements with a `google` / `microsoft` block.
    Connector
    Destructive
    API key
  • UNIFIED MARKETING OVERVIEW — in a single call, aggregates ALL connected Google sources as a funnel: Paid (Google Ads: spend/clicks/conversions) + Organic (Search Console: clicks/impressions/position) + Site (GA4: sessions/users/conversions) + Video (YouTube: views/watch time/net subscribers) + Local (Business Profile: locations/rating). Returns only CONNECTED sources; if one errors, the others still come through. SCOPE: the response's `scope` block states exactly which Google Ads account, Search Console property and GA4 property the numbers cover. customer_id targets a specific Google Ads account (empty = the selected one). site_url targets a specific Search Console PROPERTY on a multi-site account (e.g. 'kenbiltercume.com.tr' or 'https://kenbiltercume.com.tr') — the organic figures are then locked to that property; if the site is not among the connected properties `scope.site_matched` is false and the available properties are listed rather than silently reporting another site.
    ConnectorOAuth
  • LLM-ranked natural-language search over public or owned templates. This does not perform lexical query prefiltering. Use list_templates with search=... for deterministic metadata filtering.
    ConnectorOAuth