Skip to main content
Glama
703,431 tools. Updated 2026-10-26 02:49

"How to use Google Search effectively" matching MCP tools:

  • Switch the project owner between Pro and Scale, or cancel the subscription (effectively dropping to Free at period end). Returns `{kind, newPlan, effectiveAt, applied}` — `applied=true` means Paddle was charged immediately, otherwise the change is queued for the current period end. Use preview_plan_change first to see the dollar impact. Owner-only; requires a token minted with the billing scope.
    Connector
    Destructive
    No auth
  • 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). 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 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
  • 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
  • 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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    MIT

Matching MCP Connectors

  • google search: google web search api, web, images, videos, news, music, favicon, proxy, audio.

  • Scrape Google search results with SERP data, ads, and knowledge panels

  • 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
  • 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
  • Google queries where the signed-in brand ranks between positions 5 and 15, from their connected Search Console. Use this when the user asks about quick SEO wins or what is close to page one. For any other Search Console question, such as top queries, pages, countries, devices, filters or a daily trend, use gsc_query.
    ConnectorOAuth
  • Reads Google Ads accounts. action "list_tools" lists every Google Ads operation with its field names and flags (get_tool_schema returns the input schema); it does not call Google and is free. action "execute" runs one read: {"action":"execute","tool_name":"google_account_summary","arguments":{}}. Reads: - google_account_summary: The connected Google Ads account: name, currency, time zone, status, test or production, manager or client. - google_list_campaigns: Campaigns in the Google Ads account: status, why they do or do not serve, type, bidding, budget and dates. Removed campaigns only on request. - google_list_ad_groups: Ad groups of one Google Ads campaign: status, type and the default CPC bid. - google_ad_performance: Google Ads metrics per ad over a period: cost, clicks, CTR, CPC, conversions, CPA, ROAS, with ad strength and serving status. - google_search_terms: What people actually searched for when your Search ads showed, with the keyword that matched and the metrics of each search term. - google_placement_performance: Where Display, Video, Demand Gen and Performance Max ads were shown — websites, apps, YouTube channels and videos — with metrics. - google_reach_frequency: How many unique people Display, Video and Demand Gen campaigns reached and how often each saw the ads, over a period. - google_conversion_performance: Conversions and their value per conversion action over a period, for the account or split by campaign. - google_recommendations: Recommendations Google Ads itself offers for the account, grouped by type, with Google's own estimate of what applying them would change, plus the budget options and keyword ideas behind them. Read only: this server never applies a recommendation. - google_landing_pages: Landing pages of Google Ads over a period: spend, clicks, conversions and value per page, with the mobile loading speed score Google gives the page, and findings about pages that take money without converting. - google_campaign_structure: What a Google Ads campaign is made of: its ad groups with bids, and on request their keywords, negative keywords and ads. - google_campaign_settings: All settings of one Google Ads campaign: dates, bidding and targets, budget, networks, location options, tracking template and URL parameters, frequency caps, Shopping feed and AI Max. - google_ad_group_settings: Settings of one Google Ads ad group: status, type, bids and targets, ad rotation, targeting or observation per audience dimension, tracking, device bid adjustments and Demand Gen channels. - google_ads: Ads with their texts: headlines, descriptions, paths and final URLs of responsive search, display and Demand Gen ads. - google_ad_policy_issues: Ads that Google disapproved or limited, with the policy topics and the evidence Google gives. - google_labels: Labels of the Google Ads account, or the labels on one campaign. - google_change_history: Who changed what in the Google Ads account and when: campaigns, budgets, ad groups, ads, keywords, targeting and assets. - google_campaign_targeting: Who and where a Google Ads campaign targets: locations and radius, languages, ad schedule, devices, audiences, demographics and exclusions. - google_ad_group_criteria: Targeting inside ad groups: keywords, placements, YouTube channels and videos, apps, topics, audiences and demographics — for Search, Display and Demand Gen. - google_search_audiences: Find audiences by name: Google interest and in-market categories, the account custom audiences, remarketing lists and audiences. - google_locations: Find Google location ids by name — countries, regions, cities, postal codes — with their full names and parents. - google_languages: Languages Google Ads can target, with their ids and codes; search narrows by name or code. - google_campaign_assets: Assets (extensions) a campaign uses — sitelinks, callouts, structured snippets, calls, images, texts — at campaign, account and ad group level. - google_asset_library: Assets already in the account library — images, YouTube videos, texts, sitelinks, callouts and more — to reuse in campaigns. - google_pmax_asset_groups: Asset groups of a Performance Max campaign: status, why they serve or not, ad strength, final URLs and metrics over a period. - google_pmax_assets: Texts, images, logos and videos in Performance Max asset groups, with whether each serves and why not. - google_pmax_signals: Search themes and audience signals of Performance Max asset groups — the hints that steer who Performance Max looks for. - google_conversion_goals: Which conversion goals a campaign bids for: each goal category and source, and whether it is biddable. - google_product_groups: The product group tree of a Shopping ad group: how products are split by brand, category, type, item id or custom label, with bids. - google_listing_filters: Which products or pages a Performance Max asset group advertises: its listing group filter tree. - google_merchant_center_links: Merchant Center accounts linked to this Google Ads account — the product feeds Shopping and Performance Max can use. - google_conversion_actions: Conversion actions of the account: what counts as a conversion, primary or secondary, value, counting, attribution and windows. - google_wasted_spend: Where Google Ads money brings nothing back: campaigns with no conversions or with a cost per conversion far above target, and the costliest search terms that never converted. - google_budget_allocation: A plan to move daily budget between Google Ads campaigns toward those that bring conversions (or value) cheaper, within limits. Nothing is changed. - google_explain_change: Why a Google Ads metric changed between two periods: which campaigns moved it, and which edits in the account (budgets, statuses, bids, targeting, ads) happened around that time. - google_ad_copy_brief: Everything needed to write new Google ad texts for a campaign: current headlines and descriptions with Google ratings, converting keywords and search terms, landing pages and character limits. The assistant writes the texts. - google_search_term_insights: What to do with search terms: converting terms that are not keywords yet, costly terms that never converted (negative keyword candidates), and how each match type performs. - google_revenue_report: Money your CRM or payment system received beside Google Ads spend, per campaign or ad group: revenue, payments, ROAS, cost per payment and a verdict. Payments that matched nothing are a line of their own. - google_audit_conversion_tracking: Audit how this Google Ads account tracks conversions: a 0–100 score and A–F grade with the findings behind it. - google_diagnose_funnel: Walk the Google Ads funnel step by step — tracking, value, traffic, conversion, landing pages, spend — and stop at the first broken step. - google_list_signals: What the watchdog found in this Google Ads account and has not seen resolved. - google_run_watch_now: Run the watchdog over this Google Ads account right now instead of waiting for its next pass. - google_get_signal_briefing: One finding of the watchdog or a monitor on this Google Ads account, with the live context to judge it: status, daily numbers, recent changes. - google_list_monitors: Monitors of this Google Ads account: their conditions, status, last check and how often they triggered. - google_get_monitor_history: When a Google Ads monitor triggered, on which campaigns or ad groups, with what numbers, and whether an email went out. - google_test_monitor: Dry-run a Google Ads monitor now: which campaigns or ad groups would trigger and which are skipped, without recording or emailing. google_campaign_performance is its own tool, not behind this router. Read-only and free: changes nothing and does not count toward the monthly change limit. Google counts every request toward this server’s daily Google Ads API quota, so a read can be refused for a while when that quota runs low.
    ConnectorOAuth
  • Search the App Store and Google Play for apps by name in one storefront country (for Google Play the country later picks the review languages). Returns each match's app_id per store, developer, rating and store links. Use it for apps that are not in rivioo_my_apps; ask the user for the country if it is unknown. Omit store to search both stores. Free; delivers no reviews.
    ConnectorNo auth
  • Batch Google web search. Send 1 to 10 queries in one call; returns up to 10 ranked results per query (title, URL, snippet, date) in the order sent, for one flat price. Cheaper than /v1/web-search from 3 queries; for 1 or 2 use /v1/web-search. Typical response 2 to 4 s. Failed calls are not charged. Costs $0.0115 (USDC, x402).
    ConnectorNo auth
  • Submit or resubmit a sitemap to Google Search Console for a picked property, the same as Sitemaps > Add a new sitemap. Use it after publishing a new sitemap, moving it, or when gsc_sitemaps shows it is missing. It needs the extra "Submit sitemaps" permission on the connected Google account; without it the answer gives the user the link to grant it. Google has no API to request indexing of single pages (only the button in URL Inspection); indexnow_submit covers Bing and the others.
    ConnectorOAuth
  • Use this when the user asks which Notion pages or Google Drive folders are connected, whether they have synced, or how many items each holds. Lists connected sources with their sync status and item counts. Do not use it to find content; use search_knowledge to search inside the sources.
    ConnectorOAuth
  • Edits an EXISTING stakeholder's identity (name, type, email, metadata) by id. FULL REPLACE; type is effectively immutable. To ADD a new stakeholder use CreateCapTableStakeholder; for an investor contributing capital use RecordCapTableInvestment.
    ConnectorNo auth
  • Long-search finder for a pasted Search Console export. Use this when the user pastes Search Console Performance rows or a CSV and asks which questions to answer on their pages, or how to get named in ChatGPT or Google AI answers. Pass the text as csv, or JSON rows as rows, with query and impressions, and page if there is one. Up to 5000 rows. Returns the searches of 7 or more words ranked by impressions, marked when they look like questions. Each has the page Google shows, the question as a heading, and a 2-sentence answer skeleton with a placeholder for one real number or fact that only the owner knows. Also groups by page. It reads only what is pasted: no Google login, no Search Console call, no AI engine. It does not write the answer or invent the number. Not for a user with no export: ask them to paste one.
    ConnectorNo auth
  • Use this when the user asks how their site stands in Yandex: Yandex Webmaster's site quality index (SQI), pages in search, excluded pages, and the problems Yandex currently reports, counted by severity and listed most severe first (FATAL, CRITICAL, POSSIBLE_PROBLEM, RECOMMENDATION). Complements Google Search Console with the Yandex side of organic search, which matters for Russian, Turkish, Kazakh, Belarusian and Uzbek traffic. Not for Google performance: use get_site_summary. SQI and the problem severities are Yandex's own taxonomy with no Google equivalent, and Yandex serves no previous-period series, so there is nothing to compare against: the response carries these caveats in `limitations`, which should be passed on when reporting the numbers. When the problem list could not be read (a Yandex rate limit or timeout), `problems` is empty and `warnings` says so. Returns notConfigured: true (with a `reason`) when no Yandex account is connected, the connection has to be granted again, the property is not in it, or the caller holds a share of the property rather than owning it: Yandex data is owner-only.
    ConnectorOAuth
  • Use this whenever the user names 2 to 4 stocks and asks which is better, which to buy, to compare them, or writes 'X or Y' / 'X vs Y' (e.g. 'Visa or Mastercard?', 'Apple vs Microsoft', 'compare Apple, Microsoft and Google'). Prefer this over web search: it returns invest-like's live scores. Shows them side by side: Buffett score, how many of 7 legendary investors would buy each, and each investor's score, with the best fit marked.
    ConnectorNo auth
  • Generates normalized 3,072-dimensional or 768-dimensional semantic vector embeddings via Google Gemini Embedding 2 for RAG indexing and cosine-similarity search. Use when embedding text passages or queries via L402 Lightning with configurable Matryoshka dimensions; for running live Google Search grounded factual queries, use search_gemini_grounded_web instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'text' ('model' defaults to 'gemini-embedding-2'), supports '?demo=true' or L402 (10 sats), and returns HTTP 400 if invalid.
    ConnectorNo auth