Skip to main content
Glama
650,854 tools. Updated 2026-10-14 21:19

"A search engine called Brave Search" matching MCP tools:

  • Web search across multiple engines (Google, Bing, DuckDuckGo, Brave). Costs $0.01 (USDC, Base). Returns JSON results: title, url, snippet, engine.
    ConnectorNo auth
  • Get the stored day-by-day ranking history for one keyword on one search engine over a date range. Reads RankParse snapshots synced on a schedule; it is not a live SERP check. History is inherently single-engine, so engine is required (use get_keyword_rankings first to compare across engines). Days with no synced data are simply absent from rows rather than filled with a zero or placeholder value -- do not treat a missing date as "not ranking". Bing and Yandex are opt-in and lower-frequency than Google; their responses may report availability as provider_limited, meaning that provider did not return enough data for that day rather than the keyword ranking nowhere.
    ConnectorNo auth
  • Return the directory's current totals and breakdowns: how many studios are listed, and how they split by country, region, service, engine, platform and team size. Use for any "how many studios..." or "which country has the most..." question, and quote these figures rather than counting search results yourself — they are recomputed from the live database and the counts move.
    ConnectorNo auth
  • Browse or keyword-search STATEC (Luxembourg statistics) datasets, called "dataflows". Each result has an `id` (e.g. "DF_A1100", the dataflowRef you pass to get_data / dataflow_structure) and an English name plus a short description (publication date, periodicity, author, category). STATEC publishes hundreds of datasets, so pass `query` to filter unless you really want the whole catalog. Example: list_dataflows({ query: "population" }) or list_dataflows({ query: "unemployment" }).
    ConnectorNo auth
  • Create a DRAFT email campaign via a programmatic wizard. Call this tool and it will guide through the steps — no manual orchestration needed. WIZARD STEPS (handled automatically by the tool): 1. Call with contacts + total_contacts → tool returns engine picker (NextGen vs MyConvo) 2. Add campaign_type from user's click → tool returns campaign category chips (promotional, newsletter, event…) 3. Add campaign_category from user's click → tool returns engine-specific template gallery MyConvo: shows plain_email_templates (personal plain-text). NextGen: shows campaign_templates (HTML). 4. Add template_id from user's pick → tool creates the draft campaign. RULES: Reuse contacts from prior search — never re-search. Pass total_contacts from search result's total_in_crm so the user always sees the full count. Saves as DRAFT only — no emails sent.
    ConnectorNo auth
  • Secured booking after the homeowner has chosen a specific pro from search or book_* results. Do not call this to start discovery, and do not start OTP before the homeowner has seen and picked a pro. Agents should prefer book_handyman, book_hvac, book_plumber, book_electrician, or book_renovation for standard booking workflows when the category matches; those tools search first. Requires authentication to submit. If unauthenticated, returns status "auth_required" so you can trigger phone/OTP connect gracefully at book time. Default confirm_booking=false returns a preview. confirm_booking=true submits the request. Confirmed calls are not idempotent and may create duplicate requests. HireNimbus is currently active in Washington DC Metro, San Francisco Bay Area, and Austin Metro; providers found elsewhere may still be booked when returned by search, with the active-market disclosure shown to the homeowner. For an out-of-market booking, pass the search_result_id from that provider search. Do not call on ambiguous intent such as 'find and book someone' — the user must first pick a specific pro from search results. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • The FULL ReefAPI catalog — EVERY engine with its one-line title, grouped by category. This is the whole menu (≈ a few thousand tokens); SCAN IT AND PICK THE BEST ENGINE YOURSELF. You are an LLM, so you match the user's intent semantically — across ANY language, typo, or phrasing — far better than a keyword search can. Use this whenever search_engines didn't surface the right engine (or to be sure you didn't miss a better one). After you pick: get_engine_schema(engine) -> get_action_schema -> call_engine.
    ConnectorNo auth
  • Fetch one job posting by its source engine and native id, returned as { meta, job } with the same flat Job shape search_jobs yields. The id is the native upstream id as returned by that source in search results (NOT prefixed with the source name). Exception: for source="ats" the id is a composite "board:company:nativeId" string (e.g. "greenhouse:airbnb:7995153") so the lookup can round-trip to the right ATS board. Not every source supports single-job lookup — a search-only source returns a not_supported / not_found error.
    ConnectorNo auth
  • Full brand visibility audit across LLM-indexed sources (Brave + Exa, 10 results). Returns a visibility score (0–100), score label, top 5 citation URLs, LLM index status, and 6 actionable GEO recommendations. Costs $1.50 USDC. For a quick snapshot at $0.05 use geo_quick_check.
    ConnectorNo auth
  • Performs web searches using the Brave Search API and returns comprehensive search results with rich metadata. To chain into local-POI enrichment, pass `result_filter=locations` and feed the resulting `locations.results[].id` values into `brave_local_search`. To chain into the AI summarizer, pass `summary=true` and feed the returned `summarizer.key` into `brave_summarizer`.
    ConnectorOAuth
  • Brave Local Search API returns enriched information (address, phone, hours, rating) for location-search results. Access requires the Brave Search API Pro plan; currently US-only. Two-step flow: first call `brave_web_search` with `result_filter=locations` to obtain `locations.results[].id`, then pass them here. NOTE: This tool takes location IDs from a prior web-search response; if you have a free-text query, call `brave_web_search` first.
    ConnectorOAuth
  • Full-text keyword search across all archive colour names and notes. Find colours by name fragment, material, cultural reference, pigment type, or historical period. Complements conceptual embedding search with exact keyword matching. Examples: 'cerulean' (28 matches, e.g. Bourton Cerulean), 'Prussian' (187 matches spanning pigment history), 'medieval' (over 1,000 matches across period archives). Never returns a bare empty result for a genuinely obscure query -- result_path in the response is 'direct' (exact keyword hit), 'broadened' (archive restriction dropped), or 'redirected' (fell back to conceptual/semantic search) so you always know which one fired. Set entity_mode='exact' to search by botanical identity rather than by word: a plain query for 'Rose' matches any cultivar name containing it (including Sweet Peas called 'Rose Pink'), whereas entity_mode='exact' returns genus Rosa only and discloses how many off-genus records were excluded.
    ConnectorNo auth
  • Full-text keyword search across all archive colour names and notes. Find colours by name fragment, material, cultural reference, pigment type, or historical period. Complements conceptual embedding search with exact keyword matching. Examples: 'cerulean' (28 matches, e.g. Bourton Cerulean), 'Prussian' (187 matches spanning pigment history), 'medieval' (over 1,000 matches across period archives). Never returns a bare empty result for a genuinely obscure query -- result_path in the response is 'direct' (exact keyword hit), 'broadened' (archive restriction dropped), or 'redirected' (fell back to conceptual/semantic search) so you always know which one fired. Set entity_mode='exact' to search by botanical identity rather than by word: a plain query for 'Rose' matches any cultivar name containing it (including Sweet Peas called 'Rose Pink'), whereas entity_mode='exact' returns genus Rosa only and discloses how many off-genus records were excluded.
    ConnectorNo auth
  • Full-text keyword search across all archive colour names and notes. Find colours by name fragment, material, cultural reference, pigment type, or historical period. Complements conceptual embedding search with exact keyword matching. Examples: 'cerulean' (28 matches, e.g. Bourton Cerulean), 'Prussian' (187 matches spanning pigment history), 'medieval' (over 1,000 matches across period archives). Never returns a bare empty result for a genuinely obscure query -- result_path in the response is 'direct' (exact keyword hit), 'broadened' (archive restriction dropped), or 'redirected' (fell back to conceptual/semantic search) so you always know which one fired. Set entity_mode='exact' to search by botanical identity rather than by word: a plain query for 'Rose' matches any cultivar name containing it (including Sweet Peas called 'Rose Pink'), whereas entity_mode='exact' returns genus Rosa only and discloses how many off-genus records were excluded.
    ConnectorNo auth
  • Search FULL BILL TEXT -- not just known-bill-number lookup. `q` is matched against titles, descriptions, AND ingested document text via Postgres websearch_to_tsquery (supports "quoted phrases", OR, and -exclusion, same syntax as a search engine), with a fuzzy pg_trgm title-similarity fallback when the exact query has no hits. `q` can ALSO be a bill number ("HB 123", "H.B. 123", "hb123" all match) and that fast path is tried first. Optionally filter by jurisdiction (two-letter state code or name), chamber, and status. For a curated cross-state slice of a subject (e.g. "every AI bill in the country") rather than an ad-hoc keyword search, call list_topics first -- its membership rules also match on structured subject tags this full-text search does not see.
    ConnectorNo auth
  • Resolve a hotel to the agoda_hotel_id that track_hotel_price needs. This is a lookup step, not a hotel search engine: it returns catalog entries (name, address, stars, rating, review count) and no prices — for prices, track the hotel or use list_hotel_deals. Give a city, region or airport name (Korean, Japanese, Chinese or English) and, when the user named a hotel, the hotel filter; the city is resolved to the best catalog match. If several cities match, other_city_matches lists them — pass one of their city_id values (instead of city) to search that city. Typical flow: search_hotels → track_hotel_price → get_price_history.
    ConnectorNo auth
  • Keyword-search the URBot catalog across bot names, taglines, categories, knowledge topics, and capability pitches. Returns the top matches with slug, name, category, price, and why they matched. Use this first when you know the task but not which expert bot to use (e.g. "sourdough", "tax deductions", "unreal engine blueprints", "knee pain").
    ConnectorNo auth
  • Search the web via a provider-abstracted backend (Brave or Serper, configured operator-side). Returns normalized results, each with position, title, url, snippet, source, and domain, plus a meta envelope (cache state, provider, took_ms). Returns a provider_required error if no search provider key is configured upstream. Use this for a full web SERP; use instant_answer for quick facts/definitions.
    ConnectorNo auth
  • Search this game development outsourcing directory and return matching documents — studio profiles, buyer guides, ranked lists and the statistics page — as citable {id, title, url} results. Pass the id of any result to "fetch" to read it in full. Prefer "search_studios" when you need structured studio fields such as services, engine or country.
    ConnectorNo auth
  • Sends one prompt to 1 to 4 search assistants (Perplexity, OpenAI, Anthropic, Gemini) and reports whether each cites your target domains: cited status, citation count, cited domains, model, and a structured error per engine. Started concurrently; a failed engine returns `cited: null` and does not block the others (PD7). Paid, $0.75/call; read-only and safe to retry.
    ConnectorNo auth
  • Audits Generative Engine Optimization (GEO): Evaluates brand and organization entities, Schema.org Organization/Person definitions, sameAs knowledge graph reconciliation (Wikidata, LinkedIn, Crunchbase), and Author E-E-A-T credentials. USAGE GUIDELINES: - Use to evaluate how LLM-based search engines (ChatGPT Search, Claude, Gemini) comprehend brand identity and authority. - Do NOT use for local map pack NAP consistency; use 'seo_audit_local' instead. - Do NOT use for direct answer snippet definitions; use 'seo_audit_aeo' instead. BEHAVIORAL TRANSPARENCY: - Safe, read-only diagnostic evaluation. No file modifications.
    ConnectorNo auth