"Campaign Monitor" matching MCP tools:

• get_monitorA

  RoutebaseA

  Get one monitor with its recent checks. The include flags pull in what the monitor detail page shows next to it: uptime and latency percentiles over 24h to 90d, the alert policy that applies (inherited or its own), its maintenance windows, and the fire/resolve history of its alerts. Use this when you already have the monitor id; to browse a project's monitors use list_monitors. Requires project context.

  ConnectorAPI key

• stage_targeting_addA

  AMZ VaultA

  Add keywords, ASIN product targets, and/or category targets to an EXISTING campaign + ad group (SP or SB) — e.g. to act on ppc_harvesting_candidates or extend a live campaign. asin_targets items take exactly one of asin | category_id | expression (raw [{type, value}] list for category refinements; SP-only). The destination must be currently ENABLED (campaign and ad group): a PAUSED destination refuses at staging, because targets there sit dormant and re-enabling the campaign would also revive its existing targets — harvest into a live campaign or stage_campaign_create a new one instead. Stages a proposal — NOTHING changes until confirm_staged_changes.

  ConnectorOAuth

• list_monitorsA

  RoutebaseA

  List the monitors of a project with their current status. Set grouped to see them as an environment → spec tree the way the sidebar shows them (paging does not apply then). Set includeStats to add 24h uptime, p95 latency and the response-time sparkline per monitor. Use this to browse monitors or find a monitor id; for one monitor with its checks use get_monitor. Requires project context.

  ConnectorAPI key

• manage_campaignA

  Metadata MCP ConnectorA

  Manage a campaign by pausing or restarting it. KEYWORDS: pause, stop, restart, resume, unpause, campaign, control, manage, halt WHEN TO USE: - User asks to "pause campaign X" - User wants to "stop campaign Y" - User requests to "restart campaign Z" - User wants to "resume campaign A" - User asks to "unpause campaign B" ACTIONS: - pause: Temporarily pause an active campaign to stop ad serving and budget spend - restart: Resume a paused campaign to continue ad serving and budget spend REQUIRED PARAMETERS: - campaign_id: The unique identifier of the campaign to manage (integer, required) - action: The action to perform - "pause" or "restart" (string, required) CAMPAIGN ID SOURCES: Campaign IDs can be obtained from: - search_campaigns_by_names tool - create_campaign tool response - Campaign management interface URLs IMPORTANT VALIDATION REQUIREMENTS: - **CRITICAL**: You can ONLY pause campaigns that are currently "Active" - **CRITICAL**: You can ONLY restart campaigns that are currently "Paused" - Before attempting to pause or restart, use search_campaigns_by_names to verify the current campaign status

  Connector

  Destructive

  API key

• campaignstack_archive_campaignA

  campaignstackA

  Archive a campaign. WARNING: this STOPS the campaign's work, and the stop is one-way. Every workflow in the campaign is paused and every automation is disabled, including search watches. Unarchiving brings the campaign back but does NOT restart any of them - you have to re-enable each one deliberately. Call this only when the user names the campaign and confirms they want its outreach stopped, not just hidden. No data is deleted: leads already in flight stay parked rather than cancelled, and the campaign keeps its history. To remove it and its data entirely, use campaignstack_delete_campaign instead. Use campaignstack_unarchive_campaign to bring it back, and campaignstack_list_campaigns with includeArchived to find archived campaigns. If the campaign is not found, use campaignstack_list_campaigns to find valid IDs.

  Connector

  Destructive

  API key

• campaignstack_list_personasA

  campaignstackA

  List all personas for a campaign: buyer archetypes with pain points, goals, and objections. Call this when the user asks who a campaign targets. Not the roadmap: campaignstack_list_phases covers that. Use campaignstack_list_campaigns for campaign IDs.

  ConnectorAPI key

• add_extensions_to_native_campaignA

  Metadata MCP ConnectorA

  Attach existing library extensions (sitelinks, callouts, etc.) to a native-structure Google Ads / Microsoft Ads campaign, so they actually serve when the campaign launches. ALSO KNOWN AS: add extension to campaign, attach sitelink, put sitelink on campaign, link extension to campaign, enable extension for campaign KEYWORDS: add, attach, link, bind, extension, sitelink, callout, campaign, native, native structure, channel first, google ads, microsoft ads, bing WHY THIS EXISTS: creating an extension only puts it in the account library — it is NOT attached to any campaign and will not serve. This tool performs the binding. WHEN TO USE: - "Add our 'Book a Demo' sitelink to campaign X" - "Attach these callouts to the native search campaign" - After create_google_sitelink_extension, when the user wants it live on a specific campaign WHEN NOT TO USE: - The campaign uses the Precision / METADATA structure — this tool covers native-structure campaigns only and will tell you so. Precision binds extensions per-creative and has no tool yet; direct the user to the platform UI. - You do not have the extension's internal id → call list_extensions first - Removing an attachment → use remove_extensions_from_native_campaign INPUTS (all required): - campaign_id: wizard campaign id - channel: GOOGLE_ADS or MICROSOFT_ADS - extension_ids: internal ids from list_extensions (the `id` field, NOT `externalId`) BEHAVIOUR: additive — existing attachments are preserved. Safe to re-run; already-attached ids are reported and left alone. ORDERING CAVEAT: add_and_edit_native_campaign_elements rebuilds the channel's native containers and CLEARS extension attachments. Attach extensions AFTER any native element edits, or re-attach afterwards. EXAMPLE: add_extensions_to_native_campaign(campaign_id=8421, channel="GOOGLE_ADS", extension_ids=[551, 552])

  ConnectorAPI key

• remove_extensions_from_native_campaignA

  Metadata MCP ConnectorA

  Detach extensions from a native-structure Google Ads / Microsoft Ads campaign. The extension stays in the account library — only the campaign binding is removed. ALSO KNOWN AS: remove extension from campaign, detach sitelink, unlink extension, take sitelink off campaign KEYWORDS: remove, detach, unlink, unbind, extension, sitelink, callout, campaign, native, native structure, google ads, microsoft ads, bing WHEN TO USE: - "Remove that sitelink from campaign X" - "Take the old promotion extension off the native search campaign" - Undoing a wrong add_extensions_to_native_campaign call WHEN NOT TO USE: - Deleting the extension from the library entirely — this only unbinds it from one campaign - The campaign uses the Precision / METADATA structure — native-structure campaigns only INPUTS (all required): - campaign_id: wizard campaign id - channel: GOOGLE_ADS or MICROSOFT_ADS - extension_ids: internal ids from list_extensions BEHAVIOUR: only the named ids are detached; other attachments are preserved. Safe to re-run. EXAMPLE: remove_extensions_from_native_campaign(campaign_id=8421, channel="GOOGLE_ADS", extension_ids=[551])

  Connector

  Destructive

  API key

• check_balanceA

  ProductClankA

  Return the connected user's ProductClank credit balance and plan. Use before launching a campaign to confirm they have enough credits (a content campaign costs 1000; a reply or quote-post boost 200; likes/reposts 300; a discovery campaign 10 to create + 12/post discovered).

  ConnectorNo auth

• list_monitor_checksA

  RoutebaseA

  List the individual checks a monitor ran, newest first — status code, response time and the timing breakdown (DNS, connect, TLS, first byte). Set onlyErrors to see just the failures. Use from and to to narrow the window. Use this for the individual checks of one monitor; for the monitor itself use get_monitor. Requires project context.

  ConnectorAPI key

• ping_slugA

  hookpulseC

  Ping that creates its own monitor on the first hit. Same slug = same monitor; 402 when the free tier is full, and then nothing is written.

  ConnectorNo auth

• create_campaignA

  Trillboards DOOH AdvertisingB

  Create a new advertising campaign targeting DOOH screens. WHEN TO USE: - Setting up a new ad campaign on available screens - Targeting specific venues, locations, or audience profiles - Allocating budget for programmatic DOOH buys RETURNS: - campaign_id: Unique campaign identifier (UUID) - name, status, budget, screen_count, dates Campaign starts in "draft" status. Use update_campaign to set status to "active". EXAMPLE: User: "Create a campaign targeting retail screens in NYC at $5 CPM" create_campaign({ name: "NYC Retail Q1", budget_cpm: 5.0, daily_budget_usd: 100, venue_types: ["retail"], targeting: { geo: { city: "New York", state: "NY" } }, creative_url: "https://cdn.example.com/ad.mp4", start_date: "2026-03-01", end_date: "2026-03-31" })

  ConnectorNo auth

• get_campaign_performanceA

  Trillboards DOOH AdvertisingB

  Get detailed performance metrics for a campaign. WHEN TO USE: - Monitoring active campaign performance - Reviewing completed campaign results - Getting per-screen impression breakdowns RETURNS: - campaign_id, name, status, budget, dates - performance: impressions, spend_estimate_usd, avg_cpm, unique_screens, avg_latency_ms - screen_breakdown: per-screen impressions and CPM EXAMPLE: User: "How is my NYC retail campaign performing?" get_campaign_performance({ campaign_id: "550e8400-e29b-41d4-a716-446655440000" })

  ConnectorNo auth

• list_monitorsA

  MERX - TRON Resource ExchangeB

  List all monitors you created with create_monitor, optionally filtered by status (ACTIVE/CANCELLED). Each row shows the full monitor UUID (pass to cancel_monitor), monitor type, target address, and status. Note: the Target column will be empty for monitor types that do not have a single watched address — specifically price_alert and balance_threshold (when watching the API key holder rather than a third-party address). For delegation_expiry and address_activity monitors, Target will always be set. Auth required (API key).

  ConnectorNo auth

• pull_monitor_csvA

  CatchAll (by NewsCatcher)B

  Download the latest monitor run's results as a CSV file. Use when: - You want the most recent monitor run output as a CSV for offline analysis or export. - Prefer this over `pull_monitor_results` when the consumer needs spreadsheet/CSV format.

  ConnectorNo auth

• pull_monitor_csvA

  CatchAllB

  Download the latest monitor run's results as a CSV file. Use when: - You want the most recent monitor run output as a CSV for offline analysis or export. - Prefer this over `pull_monitor_results` when the consumer needs spreadsheet/CSV format.

  ConnectorNo auth

• meta_ads_campaign_write_createA

  Meta Ads (Facebook & Instagram)B

  Create, update, pause or activate Meta Ads campaigns. Actions: create — new campaign (name, objective, budget required) update — change name, budget, status pause — shortcut to pause a campaign activate — shortcut to activate a campaign Objectives: OUTCOME_TRAFFIC, OUTCOME_ENGAGEMENT, OUTCOME_LEADS, OUTCOME_SALES, OUTCOME_AWARENESS, OUTCOME_APP_PROMOTION. Budgets are in cents (e.g. 5000 = $50.00). A budget HERE means campaign budget optimization: the ad sets under it must then NOT carry their own budget. Leave the campaign budget empty to budget per ad set instead. For destructive delete use meta_ads_campaign_delete. [Flattened action: create] Bulk support: accepts campaign_ids for batched execution.

  ConnectorNo auth

• undo_campaign_sendA

  FavCRMA

  Undo a campaign send during its one-minute safety buffer. Use immediately when the merchant says to stop or undo a submitted campaign.

  ConnectorNo auth

• undo_campaign_sendA

  FavCRMA

  Undo a campaign send during its one-minute safety buffer. Use immediately when the merchant says to stop or undo a submitted campaign.

  ConnectorNo auth

• campaignstack_get_campaign_topicsA

  campaignstackA

  Get all topics assigned to a campaign along with their weight (0 to 1). Topics with weight > 0.8 have active LinkedIn search watch automations. Returns topic metadata (id, name, displayName, category) and weight for each entry. Call this when the user asks what topics a specific campaign is scored or watched on. If the campaign is not found, use campaignstack_list_campaigns to find valid campaign IDs.

  ConnectorAPI key

• campaignstack_create_search_watchA

  campaignstackA

  Set up a LinkedIn search watch that automatically discovers new leads for a campaign. A search watch monitors a topic keyword on LinkedIn content search (past 24h, relevance-sorted) every ~6 hours, reading post authors and feeding them into the campaign as new leads. Call this when the user asks to start monitoring a topic on LinkedIn for a campaign. Only one search watch per topic is active across all campaigns in a workspace at a time. If another campaign already watches this topic, the new watch is created but starts disabled (ownership transfers automatically when the other campaign is archived). Use campaignstack_list_search_topics to see what topics are already watched, and campaignstack_get_campaign_topics to see topics already on the target campaign.

  ConnectorAPI key