Skip to main content
Glama
631,684 tools. Updated 2026-10-03 00:51

"How to find answers using Google search" matching MCP tools:

  • Draft yes/no answers to attributes from my_attribute_options. Each is a factual claim about the business, so only draft answers the owner has confirmed in this conversation. Creates a DRAFT only — nothing on Google changes. Show the owner the draft this returns, word for word, and publish it with publish_change only after they say yes.
    ConnectorNo auth
  • 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
  • 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
  • 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
  • For AGENCY accounts (and ShearQuery admins): switch this Claude into demo mode as a made-up barbershop, salon, barber, cosmetologist, school or supply store. Every business tool then answers as that business — its Google profile, reviews, photos, posts, appointment book and Instagram — and drafting, publishing and undoing all work, but NOTHING reaches Google, Instagram or any customer. Every result is labeled DEMO. Call it again with another type to switch; fresh: true resets that demo business to how it started. Call stop_demo to leave.
    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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to query China's GB/T 47746—2026 customer-service compliance standard, providing clause-referenced answers, self-check lists, and standard metadata via MCP tools.
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    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

  • Search the Klever VM knowledge base for smart contract development context. Returns structured JSON with matching entries, scores, and pagination. Use this for precise filtering by type or tags; use search_documentation for human-readable "how do I..." answers.
    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
  • 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
  • Search your personal knowledge base. Finds relevant notes using semantic search. Searches across ALL your vaults by default; pass vault_id to limit to one. Omit query to list the most recently updated notes instead. Pass similar_to with a note path, instead of query, to find notes like that one. Use when the user asks about their notes, vault, knowledge, or memory.
    ConnectorOAuth
  • Search a mailbox using Outlook's search syntax and return message metadata — not bodies. Searches the whole mailbox unless folderId is given. Use this to find messages, then get_outlook_message to read one, or move_messages to file them. Examples: 'from:acme.com', 'invoice overdue', 'hasattachments:yes'.
    ConnectorOAuth
  • Run the complete authenticated Google Business Profile audit for the owner this connection belongs to: every check, the score, what is failing, and the specific fix for each one. This sees what only the profile owner can see — attributes, secondary categories, services, the business description, the search terms people used to find the business, review replies, Google's pending edits and verification status — which the public audit_google_business_profile tool cannot. Requires the owner to have connected Google; call my_shearquery_account first if unsure. Results are cached for up to six hours.
    ConnectorNo auth
  • [tourradar] Search tour reviews using AI-powered semantic search. Requires tourIds to scope results to specific tours. Use this when the user asks about reviews, feedback, or experiences for specific tours. Combine with an optional text query to find reviews mentioning specific topics (e.g., 'food', 'guide', 'accommodation'). When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.
    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
  • Start a background job that finds other names the project's brand and each of its existing competitors go by in AI answers and search results (aliases, product and store names). It does not find new competitors. Poll get_job for the result, show it to the user, and add the chosen names with update_project (the brand) or update_competitor (a competitor, by competitorId), passing the full list including the names already there. shoppingEnabled also looks at Google Shopping; country narrows to one market (ISO 3166-1 alpha-2).
    ConnectorOAuth
  • Ask the book's assistant (an AI) a question about allagents: how to list, edit, claim or withdraw a card, what the badges mean, how to find and reach agents, how to use the directory from an assistant, what the book keeps. It answers only from the book's own pages, may cite up to 3 listed agents with verified badges, and says so when the book does not say. Ten questions a day.
    ConnectorNo auth
  • Ask the book's assistant (an AI) a question about allagents: how to list, edit, claim or withdraw a card, what the badges mean, how to find and reach agents, how to use the directory from an assistant, what the book keeps. It answers only from the book's own pages, may cite up to 3 listed agents with verified badges, and says so when the book does not say. Ten questions a day.
    ConnectorNo auth
  • Get average monthly search volume, competition level, and top-of-page bid ranges for a SPECIFIC list of keywords, with no expansion into related terms. Use this when the user already has keywords in mind and wants them sized: "how much traffic are these worth?". For discovering new keywords instead, use get_google_ads_keyword_ideas. Requires Google Ads to be connected and an Ads account selected. Direct the user to rankparse.com/dashboard/integrations. Returns search volume and competition data, NOT keyword rankings; use the Google Search Console tools for ranking and position data.
    ConnectorNo auth
  • Find a business that answers support questions through Alvrun, and get the identifier you need to ask one. Search by website domain for an exact match, or by name to see the candidates. Names repeat across companies, so when several come back, choose using the domain rather than the name.
    ConnectorNo auth