Skip to main content
Glama
680,666 tools. Updated 2026-10-20 10:48

"A search engine platform" matching MCP tools:

  • 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
  • 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
  • Find the data sources an account can put on a dashboard, across every platform it has connected. Use when: the user wants a source on a dashboard and you have no sourceId for it — search first, then pass what comes back to add_data_source_to_dashboard. Searches two things. Sources DashThis already holds are found straight away, whatever the platform. Sources that exist on the platform but nobody has picked yet are found only once the search names ONE connection — asking every connection would mean calling every platform — so pass 'connection' (or an 'integration' the account has only one connection to) when the first search comes up short. Returns: each source with its connectionId and providerKey, plus a sourceId when it is already set up; and the connections searched, so you can narrow to one. Rules: this creates nothing and changes nothing. If several sources could be meant, put them to the user and let them choose — never guess, because the wrong one puts another client's numbers on a report. Then: name the source, its platform and its connection when you report back — one client often has several accounts on the same platform — and its status when it is in error.
    ConnectorOAuth
  • PREFLIGHT for AI-visibility analyses: is this tracker's data complete enough to interpret? Per answer-engine platform: observed collected-prompt count for the period, latest data date, and a structural state (ready / partial / unavailable). Pass comparison_range to also get prompt-basket deltas between periods (a shrinking or grown basket means period-over-period reads need a rebaseline caveat). Run this BEFORE interpreting AI-visibility performance — a tracking gap is not a performance gap. Counts are OBSERVED collection, not the configured basket.
    ConnectorOAuth
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • [Read] Search and analyze X/Twitter discussions for a topic, with tweet-level evidence and cited posts. Aggregate social mood, sentiment score, or positive/negative split -> get_social_sentiment. Open-web pages -> web_search. Multi-platform social search -> search_ugc. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.
    ConnectorNo auth
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    ConnectorNo auth
  • 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
  • The brand's voice, platforms, post types, platform playbook, review threshold, topic inventory and any per-channel style guides for one content space. FREE. Read this BEFORE writing any draft so you write in the brand's own voice, and at the start of any content conversation to know what is already set up. `enabled:false` means the space has no content engine yet — offer setup_content_space.
    ConnectorNo auth
  • Use this when the user asks how the DocuWriter.ai platform works or requests its published product instructions. Read-only: searches DocuWriter Platform Docs and returns relevant page excerpts with source URLs. It does not search the user's Spaces or the separate API Docs, and it cannot change documentation.
    ConnectorOAuth
  • Fetch the full declension (noun/adjective) or conjugation (verb) table for a word identified by a search result's inflection handle (entry_id + word_class). Use this only when a search ran without inline forms or left a match un-expanded — a default search already returns each match's table inline. Returns Markdown plus the table as structuredContent with the shape {"result": <paradigm>} — switch on result.category ('noun' | 'adjective' | 'verb' | 'not_found') before reading the body. Tables are generated by the official Interslavic morphology engine, not attested.
    ConnectorNo auth
  • List the social media accounts connected to the authenticated user (or current team workspace). Returns id, platform, accountName, status, tags and lastUsedAt. Call this first to discover which accountIds can be used in create_post. Workspaces can hold many accounts: narrow with platform, tag or search instead of reading the whole list. Only accounts with status 'active' can publish.
    ConnectorOAuth
  • AI answer-engine (ChatGPT/Perplexity/Gemini/AI Mode) citations — NOT Google's on-SERP AI Overviews (use competitive_trends/competitive_overview for those). Use ONLY for OVER-TIME / trend questions (a time series). Citations, share of voice and positive sentiment bucketed by day/week/month/quarter for one tracker, optionally for a single AI platform or search intent. Use for "is our AI visibility going up or down?" / "AI citations over the last 3 months". If tracker is omitted, one tracker is auto-selected; multiple trackers return a picker without querying metrics. For the current snapshot use ai_visibility_citation_audit; for per-competitor breakdown use ai_visibility_competitors.
    ConnectorOAuth
  • Search the official Redpanda documentation and return the most relevant sections from it for a user query. Each returned section includes the url and its actual content in markdown. Use this tool for all queries that require Redpanda knowledge. Results are ordered by relevance, with the most relevant result returned first. If you know the user's deployment platform, pass "platform" so results from the other platform's docs are excluded. Note that "platform" filters the sections already retrieved rather than re-running the search, so it can return substantially fewer sections: on a broker-level question where most matches come from the other platform's docs, it can cut a 15-section response to 1 or 2. Omit "platform" if you would rather have more context and judge platform relevance yourself from each section's url. If you know which Redpanda version the user runs, pass "version" (use 'current' for the latest release; its release number is also accepted). Unlike "platform", "version" is applied during retrieval, so it does not shrink the result set: it stops the same page being returned once per indexed version, which is otherwise most of the response. Version-neutral docs (Cloud, Connect, Agentic Data Plane, API reference) are always included. Omitting "version" searches the latest release.
    ConnectorOAuth
  • List EveryInfra's data platforms and capabilities (90 platforms / 413 capabilities: search, detail, comments, profiles and more). Use it before everyinfra_call_api to get the platform/action, required and optional params, the per-call row limit (max_limit, or page_size for page-based actions) and the price. Pass a platform to also get allowed values, returned fields and what they mean. Free. Data collection only — for AI chat use everyinfra_chat.
    ConnectorNo auth
  • The Search Console and Bing Webmaster properties the workspace's connected accounts can read. The first console call; every other console tool takes a property from here. Use when: "what sites are in my Search Console", before any console_get_* call, or to check which engine is connected. Not for: third-party sites the user does not own, use seo_get_domain_overview. Live rankings, use seo_get_serp. Returns: List. rows[]: engine (google | bing), property (the id to pass on: sc-domain:example.com, https://example.com/ or a Bing site URL), permission (Google: siteOwner, siteFullUser, siteRestrictedUser, siteUnverifiedUser; Bing: null), verified. NotConnected when no account of that engine is connected; its connect_url is where the user connects one. Cost: 0 credits. The user's own data is free; 60 console calls per minute per workspace. Cached 1 hour. Example: {"engine": "all"}
    ConnectorAPI key
  • Use this when someone asks whether an AI answer engine names or cites a brand for a buying question, or which other brands it names. Sends one question to one search-grounded engine through its API and returns whether the brand was named, whether its domain was cited, which of the listed competitors were named, and the pages the answer cited. Each call is a fresh API request with no account history or personalization, and one question is one datapoint, not an overall visibility score.
    ConnectorNo auth
  • List the Edgegap agent skills: tested, step-by-step workflows for getting a multiplayer game online on Edgegap, with templates (Dockerfiles, matchmaker configs, Unity C# and Unreal C++ drop-ins) and known pitfalls. Before working on a game project, load the matching skill with edgegap_get_skill: edgegap-fishnet for Unity with FishNet, edgegap-purrnet for Unity with PurrNet, edgegap-unity for other Unity projects, edgegap-unreal for Unreal Engine, edgegap-manus for a browser game built with Manus, edgegap for any other engine or platform questions; it routes to the rest. No API call.
    ConnectorAPI key
  • List which AI engines, platforms and markets each Vantage tool accepts, and the per-call limits, so you can pick valid arguments before spending any quota. Use this to answer 'does Vantage cover Gemini in Italy' or 'what can I pass as engine or platform'. Costs 0 quota units - a fixed list, it never touches the data provider. Returns: {"live_answer": {"tools" (analyze_citation_coverage, analyze_citation_structure, analyze_citation_structure_batch, analyze_citation_gap), "engines" (the values for `engine`), "country" (any country name the provider accepts; for perplexity one of "perplexity_countries" or a 2-letter ISO code), "language" (language code), "max_samples", "max_keywords_per_call"}, "tracked_data": {"tools" (find_citation_leaders, analyze_citation_trend, find_cited_questions), "platforms" (the values for `platform`), "chat_gpt_market" (the only market ChatGPT has tracked data for), "other_markets" (where to get the rest), "max_trend_months", "max_compare_domains" ({"find_citation_leaders", "analyze_citation_trend"})}, "default_market" ({"country", "language"})}. A market the provider does not cover comes back as a refunded error, never a charge.
    ConnectorAPI key
  • Read the answers engines gave in one run, to see exactly what an engine said for a prompt. Each answer has the prompt text, engine, model, repetition, whether web search was used, the brands mentioned (with first position) and every citation (URL, domain, whether it is your site or a competitor's), plus a citeladder:// id for fetch. audit_id is required: take it from read_visibility_overview. Answers come 50 per page by default; pass next_cursor for more. Only core prompts are included unless cohort is comparison or all. Filters (prompt_id, domain, url, engine) combine. Use read_visibility_overview for rates and read_visibility_sources for citation totals.
    ConnectorOAuth