"A search for Facebook" matching MCP tools:

• search

  DC Member API

  GET /search — Cross-resource omni-search Cross-resource search across profiles, rooms, messages (incl. private DMs + group DMs you're in), events, and chapters in one round trip. Returns the top-N matches per resource, grouped by resource. Use this when you don't yet know which resource carries the answer — agents typically call this first, then drill into a specific `GET /search/<resource>` for more depth on a single bucket. There's no page param: when you hit the per-resource limit and want more, switch to the per-resource endpoint for that one. The events slice has a baked-in forward-looking default (events ending in the last 30 days or later, and currently enabled) — this matches the in-app "Search across DC" surface. Use `GET /search/events` directly to look further back in time. **Query syntax (`q=`):** plain words match with prefix + typo tolerance. Wrap a phrase in double quotes to require an exact ordered match — e.g. `q="remote work"`. AND/OR/NOT/parentheses are NOT parsed in `q=` — use the structured filter params below for boolean composition.

  Connector

• social_search

  socialbridge-mcp

  Search a single network for posts matching a query, returned as the unified Post[] schema and tagged with its platform. Keyless on TikTok, YouTube, and Pinterest. Instagram, Twitter/X, Reddit, and Facebook need operator-side credentials (returns credentials_required until set). Snapchat and Threads do not support keyless search (returns not_supported); LinkedIn is quarantined. To fan one query across every network at once, use search_all.

  Connector

• list_meta_posts

  Hermoso

  List the connected Facebook Page's or Instagram account's OWN existing posts — id, caption, permalink, publish date and format. THIS IS THE TOOL THAT GETS YOU THE postId every other Meta read needs: meta_post_insights, list_meta_comments and manage_meta_post all require one, and until now the only way to have a postId was to have just published it yourself with post_to_meta. Use it for "how did our last few posts do", to find a post the user describes loosely, or before backfill_posts. Pass target:'instagram' for the linked IG account (Stories are excluded — Meta's media edge does not return them); Facebook hides unpublished drafts unless you ask for them. Only ever reads a Page the brand has connected. Read-only, 0 credits.

  Connector

• post_to_meta

  Hermoso

  Publish to a connected Facebook Page, its linked Instagram, OR the brand’s Threads account — text/link/image/VIDEO/CAROUSEL. A MULTI-SLIDE creative is a CAROUSEL, not several posts: pass the slides in order as imageUrls[] and they publish as ONE swipeable post (Instagram album, Threads carousel, Facebook multi-photo post). Never publish slide 1 of a deck on its own — the creative tells the viewer to swipe. target:"facebook" (default) posts to the Page; target:"instagram" publishes a photo or Reel to the linked IG business account (needs an image or video); target:"threads" posts to the connected Threads account (text, image, or video). Works with ANY media — a finished Hermoso ad OR an arbitrary user file: imageUrl/videoUrl accept a public https URL, a data: URI, or a Hermoso /generated path; for a LOCAL file (e.g. on the user’s desktop) call upload_file first and pass the url it returns. INSTAGRAM COLLAB: pass `collaborators` (up to 3 usernames) to invite other accounts to CO-AUTHOR the post — it then shows on their profile too once they accept, which is the reach play behind every creator partnership. This PUBLISHES immediately — confirm the copy + media with the user first. Needs a connected Meta account (Settings ▸ Connectors ▸ Meta) with posting permission; Threads needs its own connection.

  Connector

• audience_360

  Autario Data Analytics Platform

  Audience 360 | the caller's OWN audience report over their connected Google Search Console + GA4 + social (Facebook Page, Instagram, TikTok) connector data, computed deterministically server-side (the exact numbers the user sees in the app | nothing re-derived, nothing estimated). Use this FIRST for any interpretation question about a user's traffic/audience ("why is my AI traffic falling", "which queries are rising", "which pages do AI assistants cite", "how is my funnel doing") | it is far more token-efficient and more faithful than rebuilding KPIs from raw connector tables. Pick only the sections you need: overview (funnel stages + audience segments), channels (weekly channel mix + AI-share shift + brand-vs-generic clicks), queries (top brand/generic queries + 28d risers/fallers + high-impression-low-click opportunities), content (per-page sessions x engagement joined with search demand + AI-cited pages), audience (countries, devices, new-vs-returning, totals), conversions (GA4 key events), social (connected Facebook Page / Instagram / TikTok reach, follower trends, top posts, post-format engagement + IG follower demographics), health (report-vs-API cross-checks). Lists are capped and weekly series bounded; every truncation is marked with an omitted count. Filter with range/channel/countries to sharpen the question. Requires the caller's own autario account (API key or OAuth) with the Audience 360 app connected | see get_app_context("audience-360") for the data map behind it.

  Connector

• search

  search

  Search the web via Aimnis. Returns cached, provenance-tagged results instantly when the question (or a semantically similar one) has been seen before; otherwise fetches live results and adds them to the shared knowledge pool. Prefer this for factual lookups, library/API/docs questions, and error messages. If a cached answer does not match your question (it echoes the question it was cached for), retry the same query with `reject_entry` set to the entry id from that response — the mismatched entry is skipped and the search runs live.

  Connector

• publish

  uplika

  Post to social channels. Channels open today: threads, instagram, youtube, facebook. Get accountIds from select_channels — do not guess which channel the person meant. Text limits differ per channel: Threads 500 characters, Instagram 2200 characters, YouTube 5000 UTF-8 bytes, Facebook 63206 characters. Over the limit nothing goes out to any channel, so shorten it before calling. Images and video both work on the channels that take them, and a carousel can mix them. YouTube is different: it takes exactly one video, no images, and it needs options.youtube.title. Its description is measured in UTF-8 bytes, so Korean and Japanese cost three per character. Instagram cannot publish text alone: every post needs at least one image or video. A single video becomes a reel there. Set options.instagram.contentType to story for a story; stories show no caption. Non-JPEG images are converted for Instagram automatically. Facebook publishes to a Page, never a personal profile. options.facebook.link makes a link post (no media alongside), and a single video becomes a reel (3-90 seconds). There are three ways to get a media id, pick by where the file is: media_from_url when it already has a public https address, media_upload_link when it is on the person's own device, media_presign plus media_complete when you can PUT the bytes yourself. Then pass the media ids here. This publishes immediately on every channel except two that take native scheduling: YouTube with options.youtube.publishAt while privacyStatus is private, and Facebook feed posts with options.facebook.scheduledPublishTime (10 minutes to 28 days out). If the user asks to schedule anywhere else, tell them uplika cannot do that yet. A YouTube video published before Google finishes reviewing this app is locked to private viewing, so say that when you report a YouTube post as done. Returns while the post is still publishing. The permalink is null at that moment. Call get_post with the returned id to see the final status and link. Pass wait: true to hold the response until it is really out — then you can tell the person it is posted instead of guessing. For a long post use threadItems instead of publish-then-reply: we keep the order and wait for each piece to land before sending the next one.

  Connector

• list_meta_pages

  Hermoso

  List the Facebook Pages (with any linked Instagram business account) and ad accounts on the connected Meta account — use before post_to_meta / create_meta_campaign to pick the target. Requires the user to have connected Meta (Settings ▸ Connectors ▸ Meta); returns a connect hint if not.

  Connector

• pull_competitor_ads

  Hermoso

  THE FAST PATH for "show me the ads <brand> is running" — one named brand’s real live ads from the META (Facebook/Instagram) ad library, deduped, sorted, with the right page resolved. A single call, back in a few seconds. Prefer this over research_ads whenever the brand is named. Meta only, deliberately: it has by far the richest creative and is what people mean by "their ads". For Google or LinkedIn specifically, use search_google_ads or search_linkedin_ads. Spends credits.

  Connector

• search

  Whatic IC Datasheets

  Search the datasheet corpus; returns hit records (metadata + snippet, each with an opaque `ref`). Pass a ref list to `get_segments` for full content. If you already know the part number(s), prefer `lookup` — it fuses this search with `get_segments` in one call and groups full content per part. Use `search` when the part is unknown, or to triage snippets before pulling full content. For part-specific queries, pass scope='device:<MPN>' (e.g. scope='device:NE5532') to restrict hits to that part and avoid cross-part contamination.

  Connector

• search_community

  Heista

  Community-discourse search via parallel.ai with optional platform filtering. Returns synthesized text excerpts plus direct URLs to real Reddit threads, X posts from named operators, Substack essays, LinkedIn posts, Facebook posts. Use for: "what are practitioners saying about X", recurring themes in founder voice, multi-platform discourse mapping, verbatim quotes from named individuals. Per Phase 3.5 empirical A/B (Docs/solutions/architecture-decisions/search-backend-architecture-jun04.md): this tool SOLVES the Reddit/X retrieval gap that perplexity_search fundamentally couldn't fill. Optional platforms[] to restrict (e.g. ["reddit","x","substack"]). Per social-listening-synthesis §3 sample ≥3 platforms per brief.

  Connector

• check_social_preview

  Superflow Free Tools

  Read a page's Open Graph and Twitter card tags and report how the link will render on X, LinkedIn, Facebook, Slack, Discord, and Google. Returns a per-platform preview (title, description, image) plus the findings for tags that are missing, truncated, or the wrong size. Returns { ok, report: { previews[] per platform, tags, summary, findings[] }, cached, ageSeconds }. Limit: 10 runs per hour per IP. Allow up to 75s for a response. Free, no account, no API key.

  Connector

• tourradar_vertex-review-search

  MolTravel

  [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.

  Connector

• adcritter_get_api_reference

  AdCritter for Builders

  Returns the REST API contract for an AdCritter entity. Without an action parameter, returns a summary with available action names - use this to discover what you can do. With an action parameter (e.g., 'create', 'list', 'get'), returns the full details for that action: route, HTTP method, request schema, response schema, error codes, and constraints. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, canva, domain, facebook, geo, googleads, media-asset, me, plan, report, segment, settings, targeting.

  Connector

• search

  sponsorable

  Search Sponsorable's podcast-sponsorship database for brands that sponsor podcasts — the deep-research/Responses-API compatibility interface, paired with fetch. Matches sponsor names and domains and returns citable documents; pass a result's id to fetch for the full profile. For filtered or paginated search (category, industry, recency), use search_sponsors instead.

  Connector

• social_comments

  socialbridge-mcp

  Comments / replies on one post as the unified Comment[] schema, tagged with its platform. Provide url OR postId. Keyless on TikTok, YouTube, and Threads (and a single tweet via syndication on Twitter/X). Instagram, Reddit, and Facebook need operator-side credentials; Snapchat comments are not supported keyless; LinkedIn is quarantined.

  Connector

• search

  TestGraph

  Search reviews plus matching reviewed or unreviewed subjects. Search is lexical rather than semantic: for an ordinary question try one discriminating keyword at a time, then exact subject-name follow-ups and fetch every returned review. Continue with next_cursor until has_more is false before claiming exhaustive retrieval. Never merge records by display name: group and compare using subject_id and subject_type because unrelated subjects may share a name. Known subjects include immediate subject-to-subject connections so a location, organisation, variant or sibling discovered earlier can inform recommendations without being misrepresented as reviewed. For a location-based recommendation, do not stop when the target-town query has no direct result: also search the relevant subject type without a text query, follow reviewed subjects to parent organisations, and inspect each parent's official branch directory for the requested location before concluding there is no useful connection. Search returns collection_coverage on collection subjects and connected parents. Only coverage_status=complete permits a conclusion that a location or member is absent; partial or unknown coverage must be reported as uncertainty. Routine chain expansion does not require user confirmation. Search is lexical rather than semantic. For an ordinary user question, try one discriminating keyword at a time and retry with a subject-type-only search when necessary. A keyword hit is only a discovery step: search each candidate's exact subject name, then fetch every returned review before answering so reviews that omit the original keyword are not missed. Retrieval is deliberately softer than canonical naming. Search using the user's wording first, then try known aliases, canonical type names and useful broader/related types when needed. A search miss for one label is not evidence that the underlying subject or concept is absent. Stable IDs, not preferred labels, determine identity.

  Connector

• reviews.platforms

  Admin Substitute

  List configured review platforms (Google, Hipages, Facebook, etc) with their URLs. Useful for knowing where to direct review requests.

  Connector

• facebook_profile_reels

  captapi

  Latest Facebook page Reels — views, likes, comments, shares; newest-first without archive padding. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

  Connector

• cancel_scheduled

  Hermoso

  Remove a queued post before it goes out. Get the id from list_scheduled. Only works while it is still queued — something already published cannot be unsent (use manage_meta_post to delete a Facebook/Instagram post after the fact).

  Connector