Skip to main content
Glama
137,836 tools. Last updated 2026-05-21 03:40

"Campaign Monitor" matching MCP tools:

  • Rollback a project to a previous version. ⚠️ WARNING: This reverts schema AND code to the specified commit. Database data is NOT rolled back. Use get_version_history to find the commit SHA of the version you want to rollback to. After rollback, use get_job_status to monitor the redeployment. Rollback is useful when a schema change breaks deployment.
    Connector
  • Verify cryptographic proof of ad delivery or get campaign proofs. Requires either campaign_id or proof_payload (at least one must be provided). Two modes: 1. Verify a proof: pass proof_payload with signature fields to verify 2. Get proofs: pass campaign_id to get Ed25519-signed proofs for a campaign Uses Ed25519 signatures (v2) that can be independently verified by third parties using the Trillboards public key. WHEN TO USE: - Verifying that ads were actually delivered to screens - Exporting cryptographically signed proof records for auditors - Getting proof-of-play data for campaign transparency reports RETURNS (verify mode): - valid: boolean, reason: string if invalid, version: 'v1' or 'v2' RETURNS (get proofs mode): - campaignId, totalImpressions, proofsReturned - proofs: Array of signed impression proofs - pagination: { limit, hasMore, nextCursor } - signatureVersion, publicKeyUrl EXAMPLE (verify): verify_proof_of_play({ proof_payload: { signature: "ed25519=abc123...", timestamp: "2026-03-10T15:30:00Z", adId: "ad_123", impressionId: "imp_456", screenId: "scr_789", deviceId: "dev_012" } }) EXAMPLE (get proofs): verify_proof_of_play({ campaign_id: "camp_abc123", start_date: "2026-03-01", end_date: "2026-03-10" })
    Connector
  • Fetch complete campaign detail for one campaign. Required input: campaign_id. Output includes a campaign object with public campaign fields plus creator_wallet_address, and a separate funding_progress object with goal_amount, funded_amount, and percent_funded. Does not include creator_email. zooidfund does not verify campaign accuracy. Agents are responsible for their own verification. The platform makes no representations about campaign claims.
    Connector
  • Read your own PingShield config and lifetime stats. Returns current threshold, full whitelist/blacklist, custom message, and blocked/passed counters. Use to monitor your inbox protection and tune thresholds based on real traffic. FREE with API key — no credits deducted. Returns: { shielded, config: { min_reputation_score, whitelist, blacklist, shield_message }, stats: { total_blocked, total_passed } }.
    Connector
  • List all skill bundles — named groups of tools the agent typically uses together for a single user intent (build-flow, debug-flow, monitor-flow, discover, governance). Returns each skill's description and member tool names. Call this first when you are unsure which tools apply to a request; then call tool_search with query: "skill:<name>" to load the full bundle. Non-billable.
    Connector
  • List all saved contact segments (reusable audiences) for this tenant. Use when user says 'show my segments', 'list audiences', 'what segments do I have', or when offering audience options during campaign creation.
    Connector

Matching MCP Servers

  • F
    license
    B
    quality
    C
    maintenance
    Enables management of email campaigns, subscribers, lists, segments, journeys, templates, transactional email, and client/account settings through the Campaign Monitor API via natural language.
    Last updated
    100

Matching MCP Connectors

  • CFTC Rule 5.17(z) conflict-of-interest pre-trade check. Analyzes a Kalshi market's metadata to detect whether trading it would expose decision-makers (election candidates, government officials, athletes, regulators) to insider-trading liability. Pattern-matches against the Kalshi April 2026 disciplinary cases (Moran/Klein/Enriquez) and the CFTC Van Dyke complaint. Returns ALLOW/MONITOR/WARN/BLOCK recommendation + 0-100 score + reference cases. Cannot identify actual trader identity (Kalshi public API anonymizes users) — pair with internal surveillance for full enforcement.
    Connector
  • Get the caller's referral earnings, milestones, and free-call status. Requires Authorization: Bearer <api_key>, has no usage charge, and returns the current discount ledger without creating a new analysis. Example: call after a referral campaign to inspect earned credits. Use this when you need balances and milestones. Use get_referral_code instead when you only need the shareable token.
    Connector
  • Query cryptographically verified attributes from Lemma. Use this as the primary tool for finding documents whose attributes match given conditions (e.g., "subject's birthYear lt 2008"). Returns { results: Array<{ docHash, schema, issuerId, subjectId, attributes, isVerified, proof?: { status, circuitId, chainId }, disclosure? }>, hasMore }. The MCP layer enriches each item with an `isVerified` flag derived from `proof.status` (true when status is 'verified' or 'onchain-verified'). Use lemma_get_proof_status to monitor a specific proof; use lemma_get_schema to interpret the keys returned in `attributes`.
    Connector
  • Step 2 of the MCP donation flow. Required inputs: campaign_id, amount, reasoning, and tx_hash. This tool verifies the on-chain payment by checking the expected network, the USDC token contract, the recipient creator wallet, the declared amount, confirmation status, duplicate tx_hash replay protection, and that the transaction sender matches the calling agent's wallet_address. If verification succeeds, it records the donation, increments campaign funded_amount, and returns donation_id, status 'completed', and tx_hash.
    Connector
  • Use this when the user wants full details for one campaign, including budget, targeting, platform status, and next actions. Set includeAnalytics=true for one-campaign performance, includeDeploymentStatus=true for delivery/deployment blockers, and includeCountries=true only when the full country list is needed. Do not use this for a campaign list; use dynamoi_list_campaigns instead. After a successful launch or campaign mutation, prefer format=summary when you need a follow-up read to relay the final answer.
    Connector
  • Create a new email campaign with HTML body to send to a segmented audience. Supports variable substitution: {nombre}, {apellido}, {nombre_completo}, {email}, {telefono}, {organizacion}. Use audienceType "predefined" with audienceId "active"/"inactive"/"new"/"with_whatsapp"/"without_whatsapp", or "adhoc" with custom filters. Returns campaign ID and recipient count. Campaign starts as draft — use comms_send_campaign to execute. Requires confirm: true.
    Connector
  • List the guilds the current user belongs to, with role (Owner/Admin/Member), member count, and campaign count. Requires the guild.read scope. Each entry includes both `name` and `guildId` (shown inline as `[id: …]` and in structuredContent.idMap). Use the `guildId` verbatim for any tool that takes one; refer to guilds by `name` in prose to the user.
    Connector
  • Step 1 of the MCP donation flow. Required inputs: campaign_id, amount, and reasoning. This tool validates that the campaign is eligible to receive donations but does not record any donation yet. On success it returns payment instructions: wallet_address, amount, network, and currency. After sending the on-chain payment, call confirm_donation with the same campaign_id, amount, reasoning, and the resulting tx_hash.
    Connector
  • Comprehensive air quality assessment for a location in one call. Combines nearby monitor discovery and current readings with DAQI into a single response. Use this as the first tool call for any air quality question about a location. For long-term trend analysis, use the dedicated `trend_analysis` tool. Returns a structured 'summary' dict with purpose-appropriate sections. Present the summary description to users first. Args: location: Postcode, place name, or "lat,lon". purpose: What the user needs — "general" (default), "health" (safety/worry), "exercise" (outdoor activity), or "planning" (homebuying/school assessment/long-term).
    Connector
  • OpenAI ChatGPT Deep Research / Connectors fetch contract. Given an id returned by `search` (formatted as 'artist:<uuid>', 'campaign:<uuid>', or 'smartlink:<uuid>'), returns the full record for citation.
    Connector
  • List campaigns in the user's MachFive workspace. CALL THIS FIRST before generate_sequence or generate_batch — you need a campaign ID to generate emails. If the user hasn't specified a campaign, call this and ask them to pick one. Returns JSON array of campaigns with id, name, and created_at. Use the 'id' field as campaign_id in generate calls.
    Connector
  • Create a campsite availability alert that monitors for openings and notifies the user. Requires an Outdoorithm API key (generate at outdoorithm.com/dashboard/api-keys). The alert runs continuously, checking every 2-15 minutes depending on subscription tier. Args: api_key: User's Outdoorithm API key from their dashboard settings. campground_ids: List of campground CUIDs to monitor. All must use the same reservation provider. Get CUIDs from search_campgrounds or get_campground_details. Example: ["RecreationDotGov:232447:2991"] start_date: Earliest check-in date to monitor (YYYY-MM-DD). Required for all date types. end_date: Latest check-out date (YYYY-MM-DD). Required when date_type is "range". date_type: How dates are interpreted. "range" monitors a specific date window (default), "perpetual" monitors rolling 6 months from start_date, "specific_months" monitors only certain months each year. specific_months: Month numbers 1-12 to monitor. Required when date_type is "specific_months". min_nights: Minimum consecutive nights needed (1-14, default 1). max_nights: Maximum consecutive nights (1-14, must be >= min_nights). Omit for no max. days_of_week: Preferred check-in days as integers (0=Monday through 6=Sunday). Omit for any day. notify_email: Send email when availability found (default true). notify_sms: Send SMS when availability found (default false, requires phone on account). name: Display name for this alert. Auto-generated from campground and dates if omitted.
    Connector
  • <tool_description> Cancel a media buy campaign. This is a terminal state — cannot be reactivated. </tool_description> <when_to_use> When an advertiser wants to permanently stop a campaign. Cannot be undone. Use pause for temporary stops. </when_to_use> <combination_hints> cancel is terminal. For temporary suspension use pause instead. Remaining budget is released. </combination_hints> <output_format> Updated media buy with cancelled status. </output_format>
    Connector