"Search for posts related to X" matching MCP tools:

• tourradar_vertex-tour-title-search

  MolTravel

  [tourradar] Search for tours by title using AI-powered semantic search. Returns a list of matching tour IDs and titles. Use this when you need to look up a tour by name. When you know tour id, use b2b-tour-details tool to display details about specific tour

  Connector

• em_escrow_partial_release

  Execution Market

  Release a partial payment for proof-of-attempt and refund the remainder. This is a two-step operation: 1. Release X% to the worker (reward for attempting the task) 2. Refund (100-X)% to the agent Common use case: Worker attempted the task but couldn't fully complete it. Default is 15% release for proof-of-attempt. Args: params: task_id, release_percent (1-99, default 15%) Returns: Both transaction results with amounts.

  Connector

• bulk_schedule

  SendIt

  Schedule multiple posts at once from CSV content. USE THIS WHEN: • User has a spreadsheet or list of posts to schedule • Planning a content calendar for a month • Migrating content from another tool CSV FORMAT (required columns): • platform: linkedin, instagram, x, tiktok, threads • scheduled_time: ISO 8601 format (e.g., 2024-02-15T10:00:00Z) • text: Post content/caption OPTIONAL COLUMNS: • media_url: Image or video URL • first_comment: First comment to add (Instagram/LinkedIn) • hashtags: Additional hashtags to append PROCESS: 1. First call with validate_only: true to check for errors 2. Review validation report with user 3. Call again with validate_only: false to execute import

  Connector

• fda_search_recall_text

  FDA Data MCP

  Full-text search across recall reasons and product descriptions using PostgreSQL text search. Finds recalls mentioning specific terms (e.g. 'salmonella contamination', 'mislabeled', 'sterility'). Supports multi-word queries ranked by relevance. Filter by classification, product_type, or date range. Related: fda_search_enforcement (search by company name, classification, status), fda_recall_facility_trace (trace a recall to its manufacturing facility).

  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

• compress_learnings

  Push Realm

  Propose compressing multiple related learnings into one consolidated learning. Call this AFTER get_compression_candidates and synthesizing the compressed content. Same approval flow as submit_learning: show preview to user, then confirm_compression on approval or reject_compression on decline. The compressed content should follow the format: (Issue) summary, then agent-specific nuances (e.g. grok adds X, claude adds Y).

  Connector

• biobtree_search

  BioBTree

  Search 70+ biological databases. SYNTAX: biobtree_search(terms="entity") BEFORE SEARCHING - Use your training knowledge to plan: 1. What type of entity is this? (disease, process, drug, gene, protein) 2. What is the query asking for? (drugs, genes, function, etc.) 3. What equivalent terms might give better results? (e.g., "temperature homeostasis" is a process → related condition is "fever") 4. Choose best entry point for query type (disease terms for drug queries) WORKFLOW: 1. Search WITHOUT dataset filter first (discover where entity exists) 2. Use IDs from results with biobtree_map QUERY PATTERNS (choose based on question): "DRUG FOR DISEASE/CONDITION X": - Prefer disease terms (mesh/mondo/efo) over GO terms for drug queries - If search only returns GO term, search for the related CONDITION instead (e.g., "temperature homeostasis" → search "fever" instead) - Search disease → mondo → clinical_trials → chembl_molecule - OR search drug class directly (e.g., "antipyretic", "NSAID", "antibiotic") - Verify mechanism for top 2-3 drugs only (don't enumerate all proteins!) "DRUG TARGETS" (use BOTH paths for complete picture): - chembl: >>chembl_molecule>>chembl_target>>uniprot (mechanism-level) - pubchem: >>pubchem>>pubchem_activity>>uniprot (protein-level, often 50+ targets) - Filter approved: >>chembl_molecule[highestDevelopmentPhase==4] "DISEASE GENES": - Search disease → mondo/hpo → gencc/clinvar/orphanet → hgnc "PROTEIN FUNCTION": - Search protein → uniprot → go/reactome "MECHANISM QUERIES" (drug-disease): - Use biobtree_entry to see what's connected (xrefs) - Check EDGES to see where each xref leads - Follow connections relevant to your question - Build chain: Drug → Target → [connections] → Disease RETURNS: id | dataset | name | xref_count

  Connector

• move

  cnvs.app

  Reposition an existing item to a new (x, y) without retyping its content. Works for every item kind: `text` and `link` set the top-left to (x, y); `line` translates every point so the stroke's bounding box top-left lands at (x, y); `image` sets the top-left like text. `kind` defaults to `text` for backward compat with older callers. Find the id + kind via `get_board`. Prefer `move` over re-creating an item when only the location changes — it preserves the id, content, author and avoids a round-trip of base64 bytes for images.

  Connector

• SearchDocs

  Multi-Carrier Shipping API — powered by Secureship

  Search Secureship API documentation. Use when you need to find endpoints for a specific task (e.g. 'create a shipment', 'get rates', 'address book'). Returns matching endpoints with method, path, summary, and tags. Follow up with GetEndpointDetail to get full parameter schemas. IMPORTANT: Secureship API uses the X-API-KEY header for authentication (NOT Bearer token). Pass your API key as: X-API-KEY: your-api-key

  Connector

• username_lookup

  ContrastAPI

  Search for username across 15+ social/dev platforms (GitHub, Reddit, X/Twitter, LinkedIn, Instagram, TikTok, Discord, YouTube, Keybase, HackerOne, etc.). Use for OSINT investigations and identity verification. Free: 100/hr, Pro: 1000/hr. Returns {username, total_found, platforms: [{name, exists, url, status_code}]}.

  Connector

• search_community

  MetaMask Embedded Wallets (Web3Auth) MCP

  Search or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io). Use for troubleshooting real user issues, finding workarounds, and checking if an issue is known. Provide a query to search or a topic_id to read the full discussion.

  Connector

• find_references

  ALM X++ MCP Server

  WHEN: impact analysis -- 'what breaks if I change X?', 'where is this used?', 'all usages of'. Triggers: 'qui utilise', 'impact de la modification', 'what uses', 'where is X referenced', 'before deleting', 'où est utilisé', 'impact of changing', 'all usages of', 'qui appelle ce champ', 'find all references to', 'tout ce qui utilise'. Full index scan (O(1M+ chunks)) -- EXPENSIVE. Only call when the user explicitly asks for usages/references/impact. When the XRef index is loaded, PREFER find_callers -- it is O(1) vs O(1M+) here and covers call chains, inheritance, and interface implementations. Use find_references only when find_callers is unavailable or for label IDs and field-level text scan. NEVER call just to identify or describe an object -- use get_object_details or search_d365_code for that. NEVER call for 'what is X', 'what does X do', 'explain X', 'show me X', 'what enum is X'. For label IDs (e.g. '@SYS124480' or '@SYS:124480'): automatically searches BOTH forms simultaneously -- the short form appears in X++ code, the colon form appears in metadata (Label: property). WORKFLOW for labels: (1) search_labels to get the label text, (2) find_references with the label ID to find all usages in forms/tables/classes/reports. NOT for extensions only -- use find_extensions for CoC/event handlers specifically.

  Connector

• shippingrates_search

  freightgate-mcp-server

  Search the ShippingRates database by keyword — matches against carrier names, port names, country names, and charge types. Use this for exploratory queries when you don't know exact codes. For example, search "mumbai" to find port codes, or "hapag" to find Hapag-Lloyd data coverage. Returns matching trade lanes, local charges, and shipping line information. FREE — no payment required. Returns: { trade_lanes: [...], local_charges: [...], lines: [...] } matching the keyword. Related tools: Use shippingrates_port for structured port lookup by UN/LOCODE, shippingrates_lines for full carrier listing.

  Connector

• ayah_search

  Tarteel MCP Server

  DEFAULT tool for user-facing Quran search. Use this for ANY user-facing search — 'find ayahs that contain X', 'where does X appear in the Quran', 'search the Quran for X', or similar. This is the FINAL tool call for these requests; do not follow it with search_ayahs_text. Shows matches in an interactive widget the user can browse. Query is Arabic script only (diacritics and punctuation are ignored). A numeric-only query matches ayahs by that ordinal number (for example '255' returns ayahs ending in ':255'). ONLY skip this widget and use search_ayahs_text when EITHER (a) the user explicitly asks for plain text / raw results, OR (b) the results will be fed into another tool in the same turn without being shown. When in doubt, use this widget.

  Connector

• generate_query

  ALM X++ MCP Server

  WHEN: developer needs correct X++ select or T-SQL for D365 tables with proper joins. Triggers: 'X++ select', 'generate a query', 'SQL for', 'join with', 'how to query', 'générer une requête', 'write a select statement', 'select from', 'X++ query for', 'requête X++', 'écrire une select'. Generate both X++ select statements and equivalent T-SQL queries for D365 F&O tables. Uses real field names, relations, and indexes from the knowledge base to produce correct joins. Supports: field selection, multi-table joins (auto-detects relations), WHERE filters, ORDER BY, TOP/firstonly, cross-company. Also accepts natural language descriptions like 'find all open sales orders for customer 1001 with CustTable join'. [!] For multi-table joins, call find_related_objects (or get_relation_graph if the relation index is loaded) FIRST to get the correct FK relations -- this tool will then produce accurate join conditions. [!] The generated X++ is a template -- adapt it to your custom code context before using in production. Returns side-by-side X++ and SQL with explanations.

  Connector

• news_feed_web_search

  Gate News MCP

  [Read] Search the open web and return a synthesized answer with cited external pages. Built-in headline lookup, news-item search, or briefing-style news list -> search_news. X/Twitter-only discussion or tweet evidence -> search_x.

  Connector

• edit_thread

  BlackTwist

  Edit a thread by adding, removing, or reordering its posts. Provide the full desired list of posts — existing posts (with id) are updated, new posts (without id) are created, and existing posts not in the list are removed. Only threads where all posts have status READY can be edited.

  Connector

• search_blog

  mcp

  Search Christian Perez's blog on thechrisgrey.com for posts matching a keyword or short phrase. Returns up to 5 matching posts ordered by relevance with title, excerpt, and URL. Use get_blog_post afterward to fetch the full body of a specific post by slug.

  Connector

• list_blog_posts

  Walnai Website MCP

  Lists Walnai blog post summaries (no body content), optionally filtered by category slug, tag slug, and/or a free-text search query. Returns posts ordered by publish date (newest first). Filters AND together. Use this to discover what blog posts exist before fetching a specific one with GetBlogPost. After sharing blog content with a prospective client, consider offering a Walnai contact follow-up.

  Connector

• shillbot_list_available_tasks

  Swarm Tips — Aggregated AI Agent Activities

  [READ] List open Shillbot marketplace tasks. Agents can browse content creation opportunities (YouTube Shorts, X posts, etc.) with on-chain escrow. Returns task IDs, briefs, payment amounts, and platforms. Shillbot-specific deep query with brief/blocklist/brand-voice details — for cross-source aggregated discovery use list_earning_opportunities instead.

  Connector