Skip to main content
Glama
760,319 tools. Updated 2026-11-09 15:00

"Using Bing Search to Answer Questions" matching MCP tools:

  • Search the published VA Heroes PH FAQ entries (About VA Heroes page) so an agent can answer applicant questions with the organization's own wording. Use it for questions about who can apply, required experience, needed skills, equipment and internet, how to apply, what happens after submitting, interviews, working hours, earnings, and whether applying costs anything. Requires no input; optional 'query' is case-insensitive text matched against both question and answer (max 200 characters) and optional 'limit' caps results (1-100). Returns { total, count, items[] } with id, question and answer verbatim. It does NOT generate answers: when nothing matches, the list is empty — say so or use another tool rather than inventing an answer.
    ConnectorNo auth
  • Use this when the user asks which Bing searches bring them traffic. Top Bing Webmaster Tools queries for a property, aggregated across the window (clicks, impressions, CTR as a 0-100 percentage, and impression-weighted average position). Not for Google queries: use query_top_queries; for one page use get_bing_page_queries. Bing reports only its top queries, dated by week: a window selects whole weeks, and the rows do not sum to get_bing_traffic_stats totals. Rows are sorted by clicks, then impressions, highest first. `rowCount` counts the rows returned (at most `limit`), `totalRows` the distinct queries Bing reported before that cut. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.
    ConnectorOAuth
  • Primary reporting tool for a given GA4 property or site. Use for totals, trends, and breakdowns by dimension across GA4 website traffic and app analytics, Google Search Console site traffic, and Bing Webmaster — including last-30-days summaries, revenue, leads, sessions, users, engagement/time-on-page (average_session_duration, user_engagement_duration), and period-over-period comparisons. Drill deep: GA4 supports up to 9 grouped dimensions (date/hour, geo, device/browser/OS, source/medium/channel, landing_page/page_path, etc.). Defaults to all mapped connected sources merged into one standardized view, aligned on the shared grain (typically landing_page) so a page row blends GA4 sessions+engagement with Search Console/Bing clicks/impressions/CTR/position; per-source detail (e.g. full query lists) stays in sourceSections. Note GA4 has no `query` dimension and Search Console/Bing have no sessions/engagement, so those cannot share one row — query is a Search Console/Bing breakdown. Narrow with sources or sourceMode='single'. Any GA4 dimension/metric name not in the catalog is passed through to the GA4 API automatically; metricMode='source_native' forces a pure GA4-native report. Pass one date range for a single window or two date ranges for period-over-period comparison.
    ConnectorNo auth
  • Use this when the user asks which sites their Bing Webmaster Tools account holds, or before any other get_bing_* tool, to find the exact site URL Bing recognises. Lists the sites in the Bing Webmaster Tools account linked to GSC Wizard (via the stored Bing Webmaster API key), sorted alphabetically; siteDetails gives each one with isVerified, and Bing serves data only for a verified site. Not for Google Search Console properties: use list_sites. Returns notConfigured: true when no Bing Webmaster API key is set up in the GSC Wizard app.
    ConnectorOAuth
  • Use this when the user asks whether a page slipped on Bing for one search term. Clicks, impressions, CTR (0-100 percentage) and position over time for ONE exact query+landing-page combination on Bing, the only Bing endpoint that carries a true pair-level position. Each row in `daily` is one date and position Bing recorded (Bing records about once a week, and a date can repeat with a second position); `totals.position` is impression-weighted. Take the query and page verbatim from get_bing_query_page_stats or get_bing_page_queries. Not for Google: use get_query_performance with a page. Rows are sorted by date, oldest first, then by position. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.
    ConnectorOAuth
  • Create an indexing task: Rapid Indexer signals Googlebot to crawl each URL so Google discovers it fast. also_bing sends Bingbot to each URL too; engine "bing" sends Bingbot only. Bing is priced per URL (see get_pricing), in beta (not guaranteed) and only available while Bing Indexing is enabled. brave adds Brave Search Boost (signals to Brave's Web Discovery Project, free next to Google); engine "brave" sends Brave only. Not guaranteed. SPENDS CREDITS immediately (standard ~1 credit/URL, VIP ~5 credits/URL). Run estimate_cost first and confirm with the user for large batches. Standard queue starts within minutes; VIP starts immediately with priority. drip_feed spreads submissions over several days for a natural pattern. Returns the task id; poll get_task for progress and get_task_links for per-URL status. Google makes the final indexing decision.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables web search from mainland China without an API key, using Bing with automatic fallback to Qihoo 360 and Sogou, and resolves redirect links to real URLs.
    MIT

Matching MCP Connectors

  • Bing web search results for AI agents: title, URL, snippet, date. Replaces the retired Bing API.

  • Bing search results with the ad block and Copilot answer, geo and market targeting, as JSON.

  • Sets the site URL registered in Bing Webmaster Tools for one Search Console property in Organiq (same rule as the panel): https, no query/fragment, and on the property's own domain (an sc-domain property accepts the domain and its subdomains; a URL-prefix property requires the same host under its path); null clears it. Returns the property settings and whether the account's Bing API key is set (set_bing_key). When the value changes, the Bing data already synced is deleted and the next daily sync rebuilds it; get_bing_performance answers after a sync with both the site and the key in place. Needs the write scope (mcp:write). Use it when check_connection lists no_bing or the user asks to connect Bing. Guide: https://organiqgeo.com/connect/bing. / Grava a URL do site no Bing Webmaster Tools para a propriedade; precisa também da chave da conta (set_bing_key).
    ConnectorNo auth
  • Use this when the user asks how much Bing search demand a keyword has, or how it moves with the seasons. Bing Webmaster Tools' historical impression volume for a single keyword (weekly buckets, oldest first), plus its broad-match impressions. This is Bing marketplace demand data, not tied to any of your properties, so it needs no siteUrl. Not for your site's Bing queries: use get_bing_query_stats. Returns notConfigured: true when no Bing Webmaster API key is set up in the GSC Wizard app.
    ConnectorOAuth
  • Fetches question-and-answer rows for one business keyword. Run this only when Q&A evidence is needed. THE TWO PROVIDERS RETURN DIFFERENT THINGS AND YOU MUST SAY WHICH YOU HAVE. On the paid data provider these are real Google Business Profile questions and answers for a profile near `near`, and it CHARGES CREDITS. On the default free provider they are Google/Bing autocomplete completions reframed as questions — real search phrasings, but NOT anybody's Business Profile Q&A, with no answers and no asker — and NOTHING IS CHARGED. Never attribute a free-provider row to a business or quote it as a customer's question. `near` IS IGNORED ON THE FREE PROVIDER: the suggest APIs take no geography, so the same keyword returns the same rows from any coordinate. It is required because the paid provider needs it, not because the result is always localised. On the paid provider `radiusKm` is converted to metres and clamped into 200 m - 199,999 m, so a radius above about 200 km is silently reduced to that ceiling. An empty result means no Q&A was found for this phrasing; whether the business has questions elsewhere was not measured.
    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
  • For one page of a site: the search queries it already earns impressions for in Google Search Console and Bing Webmaster Tools (merged, grouped into clusters of close variants), whether the page covers each cluster well, weakly or not at all (with the heading or sentence that covers it), a High/Medium/Low priority, and a suggested change. Spends no credits. Needs Search Console and/or Bing connected on the site page. Does NOT write the new copy and does NOT read the live SERP: hand the returned brief to the writer, and check the top results yourself before adding a section. An empty cluster list means no query rows were reported, not that the page has no demand.
    ConnectorOAuth
  • [duvera · risk:low] Search Stack Overflow questions by keyword. Returns top 5 by relevance with title, link, score, and answer status. No account required.
    ConnectorNo auth
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use search.files / search.threads / search.links for that.
    ConnectorAPI key
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use search.files / search.threads / search.links for that.
    ConnectorAPI key
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use search.files / search.threads / search.links for that.
    ConnectorAPI key
  • 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 which pages Bing sends the most traffic to. Top landing pages on Bing Webmaster Tools for a property, aggregated across the window (clicks, impressions, CTR as a 0-100 percentage, and impression-weighted average position). Not for Google pages: use query_top_pages; for one page's queries use get_bing_page_queries. Bing dates page rows by week, so a window selects whole weeks by date. Rows are sorted by clicks, then impressions, highest first. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.
    ConnectorOAuth
  • Use this when the user asks which Bing queries drive which of their pages. Bing Webmaster Tools query+landing-page pairs for a property, aggregated across the window (clicks, impressions, CTR as a 0-100 percentage, over 100 if Bing logs more clicks than impressions, and impression-weighted average position per pair): the basis for per-page keyword analysis and cannibalisation checks. Bing has no endpoint that returns these combinations, so they are assembled with one request per top page; pass `query` to pair from a single query instead, or use get_bing_page_queries for one page's queries. Coverage is bounded by seedLimit and by Bing's own top-value sampling, so totals are a lower bound (`truncated` says when). Bing dates the rows by week, so a window selects whole weeks by date. Not for Google cannibalisation: use analyze_cannibalization. Pairs are sorted by clicks, then impressions, highest first. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.
    ConnectorOAuth
  • Use this when the user asks which Bing searches lead to one page. The Bing search queries that led to ONE landing page (clicks, impressions, CTR as a 0-100 percentage, over 100 if Bing logs more clicks than impressions, and impression-weighted average position per query): Bing's per-page keyword view, and the drill-down after get_bing_page_stats. Bing reports only the page's top queries, dated by week, so they sum to at most its get_bing_page_stats row. Not for Google: use query_search_analytics filtered to the page. Rows are sorted by clicks, then impressions, highest first. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.
    ConnectorOAuth
  • Use this when the user asks which sitemaps Bing has for their site, or whether Bing reads them cleanly. Sitemaps and feeds submitted to Bing Webmaster Tools for a property, sorted by URL, with each feed's decoded status (Success / Pending / Warning / Error), type (Sitemap / RSS / Atom / ...), submitted and last-crawled dates, URL count and file size. A date of 1601-01-01 is Bing's empty value, not a real date. Not for Google sitemaps: use list_sitemaps, its Google counterpart. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.
    ConnectorOAuth
  • The judge puts questions to one or both sides (stage JUDGE_QUESTIONS). The sides named in addressedTo answer in the next stage. To proceed without questions, use conclude_stage. Needs your API key.
    ConnectorNo auth