Skip to main content
Glama
199,125 tools. Last updated 2026-06-13 13:12

"How to use Google Search to generate answers" matching MCP tools:

  • Search npm or PyPI to estimate how crowded a package category is before you claim that a market is empty, niche, or competitive. Use this when you have a category or search phrase such as 'edge orm' and want live result counts plus representative matches. Do not use it to compare exact known package names or to infer adoption from downloads; it reflects search results, not market share. Registry responses are cached for 5 minutes.
    Connector
  • Manage end-user auth records for an app. Actions: - "list": Paginated list of app_users (id, email, provider, provider_uid, email_verified, last_sign_in_at, created_at). Pass the next_cursor from a prior response to page. - "delete": Hard-delete an app user by id. Cascades to refresh tokens and verification codes. Use this to unblock OAuth migrations when an existing email/password row collides. Parameters by action: list: { app_id, action: "list", limit?, cursor? } delete: { app_id, action: "delete", user_id } Tips: - Looking for a user by email? Call list and filter client-side; this tool does not search by email. - To switch a user from email/password to Google OAuth without deleting, just have them sign in with Google — the OAuth callback now links the existing email row in place automatically.
    Connector
  • Get or generate an investment memo for a deal. If generate=false (default), retrieves the existing memo. If generate=true, creates a new memo (~15-30 seconds). Requires a completed screen. Args: deal_id: The deal ID (from sieve_deals or sieve_screen). generate: Set to true to generate a new memo. memo_type: 'internal' (IC-facing, full risks) or 'external' (founder-facing). Default: internal.
    Connector
  • Search FTIR.fun public result pages (community-shared analyses). USE WHEN: - User asks "has anyone analyzed material X?" - Looking for prior analysis examples or case studies - Research community knowledge lookup - Want to see how others interpreted similar spectra DO NOT USE: - For new spectrum analysis (use search_ftir_library instead) - For library database search (use search_ftir_library instead) - When user provides their own spectrum data INPUT: - query: search text (e.g., "polyethylene", "PET", "pharmaceutical") OUTPUT: - results: list of public result pages with: * id: result identifier (use with fetch) * url: direct link to result page * title: result headline * text: summary of analysis * metadata: additional info (result_num, source) EXAMPLE: >>> search(query="polyethylene terephthalate")
    Connector
  • Ask Wiremi anything about ROSCAs, savings circles, the Wiremi Passport, or how Wiremi works, in the user's own words. Routes the question to the best Wiremi answer and always points to where to go next. Use this when the other tools do not exactly match what the user asked. The question text is logged (no other personal data) so Wiremi can see what real people ask and improve its answers, the way Search Console shows real search queries.
    Connector
  • Start a headless Google sign-in. Call this FIRST if you don't have an API token yet. Returns a user_code and verification_url for the user to visit, plus a device_code to use with poll_device_auth. No Bearer token required.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

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

  • Create a new website for a business. Pass a business candidate object from search_businesses to generate a website. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. The site generation happens in the background. Use get_site_status to check progress. Returns the businessId which can be used to access the site at /build/{businessId}
    Connector
  • Get answers to frequently asked questions about Savvly. Use when the user has specific questions about how Savvly works, fees, withdrawals, or regulatory status. For richer, audience-specific Q&As (employee / advisor / broker / employer), use `search_savvly_content` instead.
    Connector
  • Hand-verified evaluation items for grading an agent against the responder. Returns {items[], grader_url}. Submit answers (cell64 or fact_cid per item) to POST /v1/benchmark/grade for per-item scores. Items today: elevation recall, NDVI, find_similar neighbours. When to use: Call once at agent-onboarding time (or in CI) to fetch the canonical task list, then have the agent answer each item using its normal tool routing, and POST the answers map to /v1/benchmark/grade for a deterministic score. Lets an operator regression-check that an agent build still hits ground truth.
    Connector
  • Update an existing conversion action's settings — promote secondary to primary, change value, rename, fix currency. Conversion actions imported from GA4/UA/Floodlight/Firebase/Salesforce/Search Ads 360, Smart Campaign auto-actions, Store Visits, app-store actions, local_services_* / Local Services Ads actions, and manager-inherited actions are read-only via the API — the update call will be rejected locally before reaching Google. To check before calling: read `conversion_action.type` and `conversion_action.owner_customer` via `runScript` (e.g. `await ads.gaql(ads.queries.conversionActions)`) or write a direct `FROM conversion_action` query. LSA conversion names may appear in segments.conversion_action_name without appearing as mutable FROM conversion_action rows. To delete a conversion action, use removeConversionAction (status=REMOVED is not accepted by Google for updates). Returns changeId.
    Connector
  • Composite: list/browse the TELA apps discovered on-chain (each with its dURL, name, SCID, and doc count) — answers "what TELA apps exist?" without any external indexer. Powered by an in-process scan of the newest chain contracts. When to call: when a user wants to explore or search the TELA ecosystem ("what TELA apps are there", "show me TELA games", "is there a TELA app about X"), or to find a SCID when they do not know the exact dURL. For an exact dURL use dero_durl_to_scid; to inspect a specific SCID use tela_inspect. Input Requirements: - `query` is OPTIONAL. Case-insensitive filter matched against dURL and name (e.g. "chess", "vault"). - `limit` is OPTIONAL (default 50, max 200). Output: `{ query, total_matched, returned, truncated, apps:[{ scid, durl, name, install_height, doc_count }], index_meta, narrative, related_docs }`. The first call triggers a ~10s one-time discovery scan (cached afterward). `index_meta` discloses how much of the chain was scanned so the answer's coverage is transparent.
    Connector
  • Lists directly accessible Google Ads customers for the configured Google Ads credentials, including descriptive names when Google returns them. Use this to discover customer IDs before running Google Ads hierarchy or reporting tools.
    Connector
  • Initiate an OAuth handoff to a vendor integration (Google Ads, GA4, Search Console, Sheets, Drive, BigQuery, Meta Ads, Jira, Confluence). Returns an authorization URL the user opens in a browser. After the user clicks Allow, the connection is created and you can poll check_integration_status(handoff_id) to find out when the data is ready.
    Connector
  • User-facing render tool for Google Ads visual weekly reports. Use this directly for prompts like 'show me a Google Ads report', 'generate a Google Ads dashboard', or 'show 7/30/90-day Google Ads performance'. Do not first call google_ads_get_weekly_group_report unless you already need raw data for a non-visual answer; when this visual report renders, keep any assistant text to a brief confirmation.
    Connector
  • Get keyword ideas with real search volume, competition, and CPC data from Google Ads Keyword Planner. Provide seed keywords and/or a URL to discover new keyword opportunities. Returns avg monthly searches, competition level, average CPC, and top-of-page bid estimates. No Google Ads account connection required — works for all users. Use searchGeoTargets first to find geo target IDs for location targeting. Keyword Planner is a separate API (not GAQL) — use this tool, not runScript.
    Connector
  • Search for businesses by name, phone number, or location. Returns a list of business candidates with confidence scores. Use this to find existing businesses before creating a website. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. Examples: - "Joe's Pizza Brooklyn" - search by name and location - "555-123-4567" - search by phone number - "plumber in San Diego" - search by service and location Returns up to 10 candidates ranked by confidence.
    Connector
  • Resolves a list of Google Maps URLs into canonical Google Maps Place IDs. **When to call this tool (CRITICAL):** * Use this tool when the user provides one or more Google Maps sharing links or URLs (e.g. 'https://maps.app.goo.gl/...', 'https://www.google.com/maps/place/...', or 'https://maps.google.com/...') and you need to extract the underlying canonical Place IDs. * You can specify up to 20 URLs to resolve in a single batch request. **Input Requirements (CRITICAL):** * **`urls` (array of strings - MANDATORY):** The list of Google Maps URLs to resolve. Each URL must be a valid, single-place Google Maps URL. **Error Handling (CRITICAL):** * This is a batch processing tool. A request might return "mixed results" (e.g. some URLs resolve successfully while others fail). * The output list of `entities` is guaranteed to map 1:1 with the input `urls` indices. A failed URL resolution will result in an empty `Entity` message (no fields are set) at its corresponding index in the `entities` list. * You **MUST** check the `failed_requests` map field in the response to identify which specific URL index failed. The key of `failed_requests` represents the 0-based index of the failed URL in the request. Do not assume the entire batch call failed because of a partial failure.
    Connector
  • Search official Microsoft/Azure documentation to find the most relevant and trustworthy content for a user's query. This tool returns up to 10 high-quality content chunks (each max 500 tokens), extracted from Microsoft Learn and other official sources. Each result includes the article title, URL, and a self-contained content excerpt optimized for fast retrieval and reasoning. Always use this tool to quickly ground your answers in accurate, first-party Microsoft/Azure knowledge. ## Follow-up Pattern To ensure completeness, use microsoft_docs_fetch when high-value pages are identified by search. The fetch tool complements search by providing the full detail. This is a required step for comprehensive results.
    Connector
  • Search for airports and cities to get their identifiers for Google Flights tools. Returns: - IATA airport codes (e.g., 'JFK') for specific airports - kgmid (e.g., '/m/02_286') for cities - searches all airports in that city Use this tool when you have a city name like 'New York' or 'Paris' and need to convert it to codes that the flight tools accept. Note: Common IATA codes like JFK, LAX, SFO, LHR, CDG, NRT can be used directly without this tool.
    Connector
  • Query a RAG collection using natural language to retrieve relevant document chunks. Performs semantic search over the collection's indexed documents and returns the most relevant chunks ranked by similarity. Optionally synthesizes an AI-generated answer using the retrieved context. Parameters: - query: Natural language question or search phrase - top_k: Number of chunks to retrieve (default 5, max 20) - threshold: Minimum similarity score 0-1 (only return chunks above this score) - synthesize: If true, uses an LLM to generate a natural language answer from the retrieved chunks (default false — returns raw chunks only) - model: LLM model to use for synthesis (only relevant when synthesize is true, default: anthropic/claude-haiku-4.5) - filter: Metadata filter to narrow results (e.g. { category: "faq" }) Example — raw retrieval: Input: { app_id: "app_abc123", collection: "knowledge-base", query: "How do I reset my password?", top_k: 3 } Output: { chunks: [ { text: "To reset your password, go to Settings > Security > Reset Password...", score: 0.92, document_id: "doc_abc", metadata: { category: "faq", source: "help-center" } }, ... ] } Example — with synthesis: Input: { app_id: "app_abc123", collection: "knowledge-base", query: "How do I reset my password?", top_k: 5, synthesize: true } Output: { answer: "To reset your password, navigate to Settings > Security and click...", chunks: [ ... ], model: "gpt-4o-mini" } Example — with metadata filter: Input: { app_id: "app_abc123", collection: "knowledge-base", query: "pricing plans", filter: { category: "billing", version: "2.0" } } Use this to: - Search documentation or knowledge bases using natural language - Build AI-powered Q&A features for end users - Find relevant context for AI assistants - Power search bars with semantic understanding Common errors: - RESOURCE_NOT_FOUND: App or collection doesn't exist - COLLECTION_EMPTY: No documents have been ingested yet Idempotency: Safe to call anytime (read-only operation).
    Connector