Meta

Pause a campaign in a connected Meta account, or resume it and its eligible ads and ad sets, including individually paused ads. Resume can immediately spend the existing real advertising budget. Works for Chirply-built and other Facebook campaigns; preserves budgets and targeting. Returns verified campaign status; partial errors require a refresh before retrying.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.account_campaign_control \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "action": "pause"
  }'

Over MCP the same operation is the tool meta_account_campaign_control at https://app.chirply.io/api/mcp, same bearer token, same input.

Read a page of campaigns with delivery status, exact ad/ad-set counts, a representative creative image, live purchases, attributed revenue, ROAS and ad-spend return from a connected Meta ad account. Ad-spend return excludes non-ad costs and is not profit ROI. Filter source to chirply for campaigns created or duplicated in this account, or external for other Facebook campaigns. Omit source for both. Pass campaign_id to read its ads. A filtered page can be empty with a next cursor. Does not change ads or spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.account_campaigns_read \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_account_campaigns_read at https://app.chirply.io/api/mcp, same bearer token, same input.

List the account's connected Meta ad accounts, their currency, Business Manager owner, account status, and minimum daily budget. This does not spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_accounts_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool meta_ad_accounts_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Activate a real Meta ad. If its campaign and ad set are also active, it may immediately deliver to real people and spend the connected organization's money.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_activate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "ad_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_activate at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the public comments people left on the Facebook and Instagram posts one Meta ad runs on, newest first, with each comment's author, text, time, like count, the replies underneath it, and whether the advertiser's own Page or Instagram account answered. Read live from Meta on every call, all-time rather than a reporting window, and reported per underlying post because a dynamic-creative ad has one post per placement and Meta never merges their comments. Posts whose Facebook Page is not connected to this account, or whose connection lacks permission to read Page content, are returned as unreadable with the reason rather than as zero comments. Publishes nothing: no reply is sent, nothing is hidden, liked or deleted, and no money is spent.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_comments_read \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "ad_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_comments_read at https://app.chirply.io/api/mcp, same bearer token, same input.

Read a page of existing Chirply contacts with this exact Meta ad ID recorded in first or last website attribution or synced Facebook lead-form metadata. Returns names, email, phone and match evidence, scoped to this account and verified ad account/campaign. All-time recorded matches, independent of Meta insight dates; distinct contacts are not equivalent to Meta's aggregate lead events. Does not import contacts, send messages, change ads or spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_contacts_read \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "ad_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_contacts_read at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a real Meta ad in PAUSED state from an existing ad set and creative. It cannot deliver or spend until separately activated in Meta.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "ad_set_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "creative_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example"
  }'

Over MCP the same operation is the tool meta_ad_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Turn exactly one campaign, ad set or ad on or off in its connected Meta account. Turning on can immediately spend the existing real ad budget. Parent and child switches are preserved; paused parents still block delivery. Verifies ownership, hierarchy and the resulting status. No budgets or targeting are changed.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_object_status_set \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "object_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "level": "campaign",
    "status": "ACTIVE"
  }'

Over MCP the same operation is the tool meta_ad_object_status_set at https://app.chirply.io/api/mcp, same bearer token, same input.

Pause a real Meta ad, stopping new delivery and spend as Meta applies the change while retaining the ad and creative.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_pause \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "ad_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_pause at https://app.chirply.io/api/mcp, same bearer token, same input.

Compare each ad's last-30-day spend, impressions, reach, clicks, leads, and cost per lead in one connected Meta ad account. This reads Meta reporting data and does not change delivery or spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_performance_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_performance_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Resume one ad from a campaign launched by this account, also enabling its ad set and campaign. Can immediately spend real money at existing Meta budgets; other already-enabled ads under these parents may deliver too. Other individually paused ads stay paused. Review and schedules still apply.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_resume_delivery \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "ad_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_resume_delivery at https://app.chirply.io/api/mcp, same bearer token, same input.

Activate a real Meta ad set. If its campaign and ads are also active, it may immediately begin spending the connected organization's money up to its configured budget.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_set_activate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "ad_set_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_set_activate at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a real PAUSED Meta ad set with a daily budget and targeting. It cannot spend until activated, but its budget becomes live if its campaign and delivery are later activated.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_set_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example",
    "daily_budget": 1,
    "optimization_goal": "example",
    "targeting": {}
  }'

Over MCP the same operation is the tool meta_ad_set_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Pause a real Meta ad set, stopping new delivery and spend as Meta applies the change while retaining its budget, targeting, and ads.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_set_pause \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "ad_set_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_set_pause at https://app.chirply.io/api/mcp, same bearer token, same input.

List ad sets, budgets, optimization goals, schedules, and delivery status in one connected Meta ad account. This does not spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ad_sets_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ad_sets_list at https://app.chirply.io/api/mcp, same bearer token, same input.

List ads, delivery status, parent campaign/ad set, and creative in one connected Meta ad account. This does not spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.ads_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_ads_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Read its connected ad accounts with account IDs and business portfolio details, and Pages with advertising permission and current profile photos. Inbox routing ownership does not restrict website advertising. Read-only; spends no money and changes no ads or messaging routes.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.advertising_identity_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool meta_advertising_identity_get at https://app.chirply.io/api/mcp, same bearer token, same input.

List every custom audience on one connected Meta ad account — website visitors, lead-form activity, Page and Instagram engagement, and uploaded customer lists — with its rough size and whether Meta considers it ready to advertise to. Use it to pick an audience to retarget or to exclude. Read-only: it creates no audience, changes no delivery, and spends no money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.audiences_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_audiences_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Activate a real Meta campaign. If its ad sets and ads are eligible, this may immediately begin spending the connected organization's money according to their budgets.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_activate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_activate at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch a campaign's current Meta performance and send it to the account's OpenRouter reasoning model for saved recommendations. Billed to its own OpenRouter account. Advice only: never changes ads or budgets. Reuse request_id on retries.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_analyze \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "request_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_analyze at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a real campaign in Meta Ads Manager in PAUSED state. It cannot spend until separately activated, but it permanently creates an external advertising object.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example",
    "objective": "example"
  }'

Over MCP the same operation is the tool meta_campaign_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Move one unpublished Magic Ads draft out of the current campaign list and into the reversible archive. This does not delete creative records, contact Meta, change delivery, publish anything, message anyone, or spend money. Published campaigns cannot be archived here.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_draft_archive \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_draft_archive at https://app.chirply.io/api/mcp, same bearer token, same input.

PERMANENTLY delete one unpublished or archived Magic Ads draft and cascade-delete its saved creative metadata from Chirply. This cannot be undone. Generated image files, funnels, and automations remain in their own libraries, and this does not delete or pause anything in Meta. Published campaign records are refused.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_draft_delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_draft_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Load one tenant-scoped Magic Ads campaign account exactly where it was saved, including its brief, generated plan, creative versions, delivery settings, funnel choice, and automation choice. This is read-only and does not contact Meta or change delivery.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_draft_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_draft_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Restore one archived Magic Ads draft to the current campaign list with its brief, creative records, and saved builder state intact. This does not contact Meta, change delivery, publish anything, message anyone, or spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_draft_restore \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_draft_restore at https://app.chirply.io/api/mcp, same bearer token, same input.

Create or update a private, tenant-scoped Magic Ads draft with the exact resumable builder state. This stores data in Chirply only; it does not generate media, publish a funnel, contact Meta, launch ads, message leads, or spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_draft_save \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "campaign_name": "Example",
    "workspace": {}
  }'

Over MCP the same operation is the tool meta_campaign_draft_save at https://app.chirply.io/api/mcp, same bearer token, same input.

List every unarchived Magic Ads campaign in the current account, including drafts and launched campaigns, their objective, destination, creative count, and whether a companion funnel or automation exists. This is read-only and does not contact Meta or change delivery.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_drafts_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 100,
    "view": "active"
  }'

Over MCP the same operation is the tool meta_campaign_drafts_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a real paused copy of an existing Meta campaign including its ad sets and ads. Permanently creates external advertising objects, but does not activate delivery or spend ad budget. Requires ads management access. Reuse request_id on retries; an uncertain outcome must be checked in Ads Manager before attempting another copy.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_duplicate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "request_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_duplicate at https://app.chirply.io/api/mcp, same bearer token, same input.

Read one page of ad sets or ads within a connected campaign, with individual configured and effective delivery status, creative images, ad counts and performance for the chosen account-timezone date range. Optionally restrict ads to one ad set. Does not change delivery or spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_hierarchy_read \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "level": "adset"
  }'

Over MCP the same operation is the tool meta_campaign_hierarchy_read at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the latest thirty saved AI analyses and campaign duplication outcomes for one connected Meta ad account in this account. Does not generate new analysis, change ads, or spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_operations_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_operations_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Pause a real Meta campaign, stopping new delivery and spend as Meta applies the status change. The campaign and its configuration remain available to reactivate later.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_pause \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_pause at https://app.chirply.io/api/mcp, same bearer token, same input.

Report how every Facebook and Instagram campaign this account launched through the app is actually doing: whether each one is still in Meta's review queue, live and delivering, paused, or rejected, plus impressions, people reached, clicks, click-through rate, cost per click, amount spent, leads, and cost per lead for the chosen window — broken down per creative version. Campaigns run directly in Ads Manager are deliberately excluded, because this account did not launch them here. Read-only: it never changes delivery, never turns anything on or off, and never spends money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_results \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "window": "today",
    "limit": 25
  }'

Over MCP the same operation is the tool meta_campaign_results at https://app.chirply.io/api/mcp, same bearer token, same input.

Resume a campaign launched by this account together with all its resumable ads and their ad sets, including individually paused ads. Can immediately spend real money from the connected Meta ad account at existing budgets. Leaves targeting, schedules, rejected and archived ads unchanged; reports partial failures.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_resume_ads \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_resume_ads at https://app.chirply.io/api/mcp, same bearer token, same input.

Optionally generate and immediately PUBLISH a complete public conversion funnel for one saved Magic Ads draft, mount it below a route on a connected domain, and/or create a PAUSED editable follow-up automation using the exact Facebook Page/form and funnel triggers. AI generation consumes the account's OpenRouter credits. Publishing makes the generated pages public; the workflow does not contact anyone until a person reviews and activates it.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaign_system_build \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "business_name": "Example",
    "campaign_name": "Example",
    "offer": "example",
    "audience": "example",
    "strategy": "example",
    "form_promise": "example",
    "campaign_goal": "AWARENESS",
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaign_system_build at https://app.chirply.io/api/mcp, same bearer token, same input.

List campaigns in one connected Meta ad account. This reads campaign configuration and does not spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.campaigns_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_campaigns_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Show the comment-to-DM settings for one connected Instagram account: whether it is on, the keyword a comment must contain, the message that gets sent, and whether each commenter is messaged only once.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.comment_dm_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_comment_dm_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Set whether an Instagram direct message is sent automatically to people who comment on this account's posts. Turning this on causes REAL DIRECT MESSAGES TO BE SENT AUTOMATICALLY TO REAL PEOPLE who have not messaged the business first, every time a matching comment is posted, with no further human approval. Instagram permits one such message per comment, within 7 days of it being posted.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.comment_dm_update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "enabled": true
  }'

Over MCP the same operation is the tool meta_comment_dm_update at https://app.chirply.io/api/mcp, same bearer token, same input.

List the recent posts from one connected Facebook Page and its linked Instagram account, with the id each one is identified by. Use it to find the post id a per-post comment rule targets.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.comment_posts_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_comment_posts_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete one comment automation rule. It stops running immediately and cannot be recovered; comments it used to handle fall through to the next matching rule, or to the Page's own comment settings.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.comment_rule_delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "rule_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_comment_rule_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Create or update one comment automation rule on a connected Facebook Page. An active rule causes REAL PUBLIC COMMENT REPLIES and REAL PRIVATE MESSAGES TO BE SENT AUTOMATICALLY TO REAL PEOPLE, from its own connected account, every time a matching comment is posted and with no further human approval. Meta permits one private reply per comment within 7 days, so a rule either sends a fixed message or starts a flow, never both. When several rules match, the most specific one runs: a rule for one post beats a rule for every post, and a keyword rule beats a catch-all.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.comment_rule_save \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_comment_rule_save at https://app.chirply.io/api/mcp, same bearer token, same input.

List the comment automation rules on one connected Facebook Page: what each one matches (every post or one post, which keywords), what it replies publicly, and whether it sends a private message or starts a flow. Rules cover Messenger and the Page's linked Instagram account together.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.comment_rules_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_comment_rules_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Read this account's connected Facebook profile name, saved permission snapshot, ad accounts and business portfolios, Pages and Instagram IDs. Read live Meta Pixels for the selected connected ad account, including each ID, last-event date, availability and copyable website installation code. The code reports browser PageView events to Meta when installed and allowed by the site's marketing consent; installation and lead/purchase event setup are separate. Returns explicit read errors and a cursor for more than 100 pixels. This read installs nothing, changes no ads, sends no messages and spends no money. Never returns credentials.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.connected_assets \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "pixel_after": "example"
  }'

Over MCP the same operation is the tool meta_connected_assets at https://app.chirply.io/api/mcp, same bearer token, same input.

Disconnect Facebook and Instagram from this account, uninstall Chirply from its Pages, revoke the Meta user grant, and remove locally stored Page/ad assets. Existing CRM contacts and messages remain. Reconnecting is required to restore service.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.connection_disconnect \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "confirm": true
  }'

Over MCP the same operation is the tool meta_connection_disconnect at https://app.chirply.io/api/mcp, same bearer token, same input.

Show whether Facebook, Instagram, and WhatsApp are connected to this account, which permissions were granted, and whether Meta requires the owner to reconnect. Tokens and other secrets are never returned.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.connection_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool meta_connection_get at https://app.chirply.io/api/mcp, same bearer token, same input.

List Meta Pixels (datasets), received custom Pixel events from the last 28 days when pixel_id is supplied, and custom conversions on one connected ad account, with each Pixel's name and whether it has ever received an event. These are what a website campaign optimizes around: the Pixel watching the site, and the thing happening on it that counts as success. Read-only — it creates nothing, changes no delivery, and spends no money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.conversion_sources_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_conversion_sources_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a real unpublished Meta link-ad creative for a connected Facebook Page. This does not deliver or spend until attached to an active ad.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.creative_create_link \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example",
    "message": "example",
    "link_url": "https://example.com"
  }'

Over MCP the same operation is the tool meta_creative_create_link at https://app.chirply.io/api/mcp, same bearer token, same input.

List Instagram Professional profiles linked to this account's Facebook Pages, including current usernames, follower counts, media counts, webhook delivery, and live direct-message access status. This is read-only.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.instagram_accounts_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool meta_instagram_accounts_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Publish a REAL PUBLIC IMAGE POST to one Instagram Professional account assigned to this account. The image and caption become visible to that account's audience immediately; this does not buy ads but permanently creates external content until someone deletes it in Instagram.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.instagram_image_publish \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "instagram_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "image_url": "https://example.com"
  }'

Over MCP the same operation is the tool meta_instagram_image_publish at https://app.chirply.io/api/mcp, same bearer token, same input.

List recent posts from one Instagram Professional profile assigned to this account, including captions, permalinks, likes, and comment counts. This is read-only.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.instagram_media_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "instagram_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_instagram_media_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Create and activate a real Meta instant lead form on a connected Facebook Page, collecting full name, email, and phone. New submissions enter this account and may trigger its contact-created automations. This permanently creates an external Meta object but does not launch an ad or spend ad money.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.instant_form_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example",
    "privacy_policy_url": "https://example.com",
    "follow_up_action_url": "https://example.com"
  }'

Over MCP the same operation is the tool meta_instant_form_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Read saved launch steps, created Meta object IDs, and the latest failure for a campaign draft in this account. Shows completed, running and uncertain outcomes without creating ads, changing delivery, or spending money. Completed provider steps are reused when the existing launch action is retried with identical settings.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.launch_progress_read \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_launch_progress_read at https://app.chirply.io/api/mcp, same bearer token, same input.

Reset a failed campaign launch after verifying that its old Meta campaign is archived or deleted. Preserves the draft, settings, creative assets and prior launch history. Does not delete Meta objects, create ads, activate delivery or spend money. A separate launch action and budget approval are still required. Refuses active, uncertain, successful or concurrently changed attempts.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.launch_reset \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "run_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_launch_reset at https://app.chirply.io/api/mcp, same bearer token, same input.

Save an already-public image URL as a durable creative version in a saved Meta campaign draft, preserving the exact copy, direction, and references. This stores metadata but does not generate an image, contact anyone, create a Meta object, or spend ad money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_asset_save \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "concept_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "angle": "example",
    "image_url": "https://example.com"
  }'

Over MCP the same operation is the tool meta_lead_campaign_asset_save at https://app.chirply.io/api/mcp, same bearer token, same input.

List the account's saved Meta campaign creative versions, including every generated image, its ad copy snapshot, creative direction, reference images, model, cost, and launched Meta ad id. This is read-only.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_assets_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "limit": 100
  }'

Over MCP the same operation is the tool meta_lead_campaign_assets_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Turn one natural-language or dictated advertising brief into three editable, durably saved Meta ad concepts and recommend the best awareness, traffic, engagement, leads, sales, or app-promotion objective. The offer, audience, location, desired next step, differentiator, and tone are extracted without requiring form fields. Optionally ad hack a reference screenshot: keep its offer or adapt its format to a new offer, with an additional billed OpenRouter vision call. This uses the account's own OpenRouter model and may incur that provider's text-generation charge; it does not create anything in Meta, contact anyone, or spend ad money.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_from_spoken_brief \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "business_name": "Example",
    "spoken_brief": "example"
  }'

Over MCP the same operation is the tool meta_lead_campaign_from_spoken_brief at https://app.chirply.io/api/mcp, same bearer token, same input.

Edit a saved image in this campaign using change instructions and optional reference images. The original image is sent as the source, and the result is saved as a new version without overwriting it. Charges its own OpenRouter account and stores the result as a public image; does not launch or change a live ad.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_image_edit \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "draft_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "asset_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "changes": "example"
  }'

Over MCP the same operation is the tool meta_lead_campaign_image_edit at https://app.chirply.io/api/mcp, same bearer token, same input.

Generate one real square advertising image through its own OpenRouter account and store it as a public asset that Meta can fetch. This incurs the image model's provider charge and permanently stores the generated image, but does not create or launch a Meta ad.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_image_generate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "visual_prompt": "example"
  }'

Over MCP the same operation is the tool meta_lead_campaign_image_generate at https://app.chirply.io/api/mcp, same bearer token, same input.

Create and activate one real Meta awareness, traffic, engagement, leads, sales, or app-promotion campaign with a validated destination, CTA, and placement strategy. This immediately makes the campaign eligible to reach real people and spend the selected ad account's money up to the daily budget; Meta bills the advertiser directly. The campaign is created paused and activated last so an incomplete setup cannot spend.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_launch \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_name": "Example",
    "primary_text": "example",
    "headline": "example",
    "image_url": "https://example.com",
    "daily_budget_minor": 1,
    "location_query": "example",
    "country_code": "example"
  }'

Over MCP the same operation is the tool meta_lead_campaign_launch at https://app.chirply.io/api/mcp, same bearer token, same input.

Generate and durably save 3–10 editable Meta ad concepts from a truthful business brief and recommend the best awareness, traffic, engagement, leads, sales, or app-promotion objective. Optionally ad hack a reference screenshot: keep its offer or adapt its format to a new offer, with an additional billed OpenRouter vision call. This uses the account's own OpenRouter model and may incur that provider's text-generation charges; it does not create anything in Meta or contact anyone.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_plan \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "business_name": "Example",
    "offer": "example",
    "audience": "example",
    "location": "example"
  }'

Over MCP the same operation is the tool meta_lead_campaign_plan at https://app.chirply.io/api/mcp, same bearer token, same input.

Validate a complete Meta awareness, traffic, engagement, leads, sales, or app-promotion campaign in test mode, including its CTA and placement rules. This creates no Meta objects, contacts no one, incurs no ad spend, and does not require a live Meta connection.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_simulate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_name": "Example",
    "primary_text": "example",
    "headline": "example",
    "daily_budget_minor": 1,
    "location_query": "example",
    "country_code": "example"
  }'

Over MCP the same operation is the tool meta_lead_campaign_simulate at https://app.chirply.io/api/mcp, same bearer token, same input.

Create and activate one real Meta campaign using the selected awareness, traffic, engagement, leads, sales, or app-promotion objective, then launch every selected saved creative as a separate real ad using the shared CTA and placement strategy. If an instant-form lead destination uses form_id __auto__, this also permanently creates an active Meta form. The campaign becomes eligible to reach real people and spend the selected ad account's money up to the shared daily budget; Meta bills the advertiser directly.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_campaign_variations_launch \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_name": "Example",
    "creatives": [
      {
        "angle": "example",
        "primary_text": "example",
        "headline": "example",
        "image_url": "https://example.com"
      }
    ],
    "daily_budget_minor": 1,
    "location_query": "example",
    "country_code": "example"
  }'

Over MCP the same operation is the tool meta_lead_campaign_variations_launch at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a typed contact custom field for one question on a connected Facebook Lead Ads form, then save that form mapping immediately. Future submissions fill the field; matching existing choice fields gain the supplied choices. This changes CRM data only and sends no messages.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_field_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "form_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "question_key": "example",
    "label": "example",
    "type": "text"
  }'

Over MCP the same operation is the tool meta_lead_field_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Turn CRM capture on or off for one connected Facebook Lead Ads form and map each submitted question into a contact field. Pausing a form causes future submissions from it to be retained as ignored webhook events instead of contacts.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_form_update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "form_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "enabled": true,
    "field_mapping": {}
  }'

Over MCP the same operation is the tool meta_lead_form_update at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the connected Facebook Pages' Lead Ads form catalogs and questions, then refresh the tenant-scoped form list. Newly discovered forms stay paused until an account manager enables them. This makes Graph API reads but does not create ads, spend money, or contact anyone.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_forms_discover \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool meta_lead_forms_discover at https://app.chirply.io/api/mcp, same bearer token, same input.

List the Facebook Lead Ads forms discovered for this account, optionally narrowed to one Page or searched by form name, including questions, field mappings, capture status, and latest sync health. This only reads the saved form catalog and does not contact leads.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_forms_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool meta_lead_forms_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Read every saved original Facebook Lead Ads submission attached to one contact, including the source field_data array and readable answers. Earlier contacts without a submission record return their saved contact data as legacy_custom. This returns personal lead information without changing any data.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.lead_submissions_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "contact_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_lead_submissions_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Queue a resumable import of all Facebook Lead Ads submissions Meta currently makes available across every form on one connected Page, including forms paused for future capture. New contacts use the Facebook submission time for First added; matched contacts keep their existing First added date and retain the Facebook submission timestamp separately. Creates or enriches CRM contacts without changing future form capture settings or starting live follow-up automations. Existing contacts are matched by phone or email. Sends no messages and spends no provider money.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.leads_import_page \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_leads_import_page at https://app.chirply.io/api/mcp, same bearer token, same input.

Read saved progress and any errors for historical Facebook Lead Ads imports across all forms on a connected Page. Reads Chirply job records only and makes no Facebook request, sends no messages, and changes no contacts.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.leads_import_status \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_leads_import_status at https://app.chirply.io/api/mcp, same bearer token, same input.

Import up to 25 recent real submissions from one connected Facebook Lead Ads form. New contacts use their original Facebook submission time for First added by default. This creates or enriches real CRM contacts without starting live follow-up automations or sending messages. Existing form capture settings are unchanged.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.leads_sync_recent \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "form_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_leads_sync_recent at https://app.chirply.io/api/mcp, same bearer token, same input.

Search Meta for whole countries, states/regions, cities and postal codes within the supplied country. Returns exact location keys and labels to choose before launching ads. Pass the chosen key and original query to launch. Read-only; does not create ads or spend money.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.locations_search \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "example",
    "country_code": "example"
  }'

Over MCP the same operation is the tool meta_locations_search at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately sends a real Messenger App Event to Meta for one Page-scoped person, including the Page id, that person's PSID, the event name, optional purchase value and currency, and the two supplied tracking declarations. It sends no Messenger message and charges no money, but the signal can affect Meta analytics, attribution, optimization, and advertising, so an account owner or admin must confirm it.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_app_event_log \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "conversation_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "event_kind": "lead"
  }'

Over MCP the same operation is the tool meta_messenger_app_event_log at https://app.chirply.io/api/mcp, same bearer token, same input.

Ask Meta to fetch one public HTTPS image, video, audio, or file and create a real reusable attachment id owned by a connected Facebook Page. This sends no message and Chirply persists neither the source URL nor returned id, but the external Meta asset cannot be listed or deleted through the supported Attachment Upload API; copy the returned id immediately and expect it to expire after 90 days.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_attachment_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "type": "image",
    "source_url": "https://example.com"
  }'

Over MCP the same operation is the tool meta_messenger_attachment_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Check whether one connected Facebook Page is ready to create reusable Messenger image, video, audio, and file attachment ids. This reads Page readiness and Meta's provider limits, sends no message, returns no previous attachment ids, and makes no change. Meta's Attachment Upload API does not provide supported list or delete operations, and reusable ids expire after 90 days.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_attachment_upload_info \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_attachment_upload_info at https://app.chirply.io/api/mcp, same bearer token, same input.

Get the permanent m.me URL, QR value, and current Page delivery readiness for one saved Messenger-compatible Bot Flow. Opening the URL does not immediately send a message; after a person enters Messenger and taps Get Started when required, the link starts exactly that live flow and its real outbound messages. Draft flows remain inert until published.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_bot_flow_link_generate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "bot_flow_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_bot_flow_link_generate at https://app.chirply.io/api/mcp, same bearer token, same input.

Accept a real inbound Messenger call to the connected Facebook Page using the provider call id and supplied WebRTC SDP offer. Meta requires acceptance within 60 seconds, and the calling client must remain connected to carry the media.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_accept \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "call_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "sdp": "example"
  }'

Over MCP the same operation is the tool meta_messenger_calling_accept at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately place a real outbound Messenger audio/video call from the connected Facebook Page to one known person using the supplied WebRTC SDP offer. The person must have live call permission and Meta must report start_call is allowed; the calling client must remain connected to carry the media.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_connect \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "sdp": "example"
  }'

Over MCP the same operation is the tool meta_messenger_calling_connect at https://app.chirply.io/api/mcp, same bearer token, same input.

Validate and prepare one RFC4733 touch tone for a real active Messenger call. The returned browser command always uses Meta's required 500 ms duration and 100 ms inter-tone gap; it does not falsely claim that the server injected RTP because the live WebRTC sender exists only in the open softphone, which must consume the command. Meta emits no DTMF webhook.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_dtmf_prepare \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "call_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "tone": "0"
  }'

Over MCP the same operation is the tool meta_messenger_calling_dtmf_prepare at https://app.chirply.io/api/mcp, same bearer token, same input.

Read one connected Facebook Page's live Meta Calling eligibility, current audio/video/icon/hours/routing settings, webhook and permission readiness, known Messenger people, and recent call events. This sends no message and changes nothing; Meta's messenger_api_calling status remains the authoritative review/availability gate.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_calling_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Renegotiate the live audio/video tracks of a real active Messenger call using increasing media versions, the actual browser MediaStreamTrack ids, and a new WebRTC SDP offer containing those ids. This can immediately mute, unmute, enable, or disable camera media for both participants' live call experience.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_media_update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "call_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "from_version": 1,
    "to_version": 1,
    "audio_enabled": true,
    "video_enabled": true,
    "sdp": "example"
  }'

Over MCP the same operation is the tool meta_messenger_calling_media_update at https://app.chirply.io/api/mcp, same bearer token, same input.

Submit the finished real Messenger call's end reason and optional browser audio-quality counters to Meta. Meta accepts this once per call, only after the call ends, and only within 24 hours; it changes provider analytics rather than contacting the person.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_metrics_submit \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "call_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "end_call_reason": "Call_End_Accept_After_Hang_Up",
    "call_ended_time": 1
  }'

Over MCP the same operation is the tool meta_messenger_calling_metrics_submit at https://app.chirply.io/api/mcp, same bearer token, same input.

Read Meta's live outbound-calling permission and per-action limits for one known person in a connected Facebook Page's Messenger thread. This sends no message and does not infer permission from Chirply data.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_permission_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example"
  }'

Over MCP the same operation is the tool meta_messenger_calling_permission_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Send a real Messenger calling_optin template to one known person, asking them to approve outbound calls from the connected Facebook Page. Meta allows at most two permission requests per thread in 24 hours and grants expire after seven days; the person may reject the request.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_permission_request \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example"
  }'

Over MCP the same operation is the tool meta_messenger_calling_permission_request at https://app.chirply.io/api/mcp, same bearer token, same input.

Send a real Messenger call_prompt template that lets one known person call the connected Facebook Page for one to seven days, including when its persistent call icon is hidden. This immediately messages a real person and Meta rejects it until Calling is enabled.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_prompt_send \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "ttl_days": 1
  }'

Over MCP the same operation is the tool meta_messenger_calling_prompt_send at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately decline a real inbound Messenger call to the connected Facebook Page. The caller's ringing attempt ends and this action cannot be undone.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_reject \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "call_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_calling_reject at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately start, stop, or restore screen-share video in a real active Messenger call by sending Meta's current media_update contract with increasing versions, a browser-created SDP offer, and the exact getDisplayMedia or restored-camera MediaStreamTrack ids. The browser must obtain the person's screen-sharing permission and keep the live WebRTC peer connected; this operation changes what the other participant sees.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_screen_share_update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "call_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "from_version": 1,
    "to_version": 1,
    "audio_enabled": true,
    "video_enabled": true,
    "video_track_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "sharing": true,
    "sdp": "example"
  }'

Over MCP the same operation is the tool meta_messenger_calling_screen_share_update at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately terminate a real active Messenger call on the connected Facebook Page. The other participant is disconnected and this action cannot be undone.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_terminate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "call_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_calling_terminate at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately replace the connected Facebook Page's live Messenger Calling audio, video, call-icon, weekly-hours, timezone, and ring-target settings. META rings Meta's native surface; PARTNERS sends real inbound calls to Chirply's browser softphone and requires the calls webhooks. Meta rejects this operation until the Page and app pass its Calling access/review gate.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_calling_update_settings \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "audio_enabled": true,
    "video_enabled": true,
    "icon_enabled": true,
    "timezone_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "weekly_operating_hours": [
      {
        "day_of_week": "MONDAY",
        "open_time": "example",
        "close_time": "example"
      }
    ],
    "ring_target": "META"
  }'

Over MCP the same operation is the tool meta_messenger_calling_update_settings at https://app.chirply.io/api/mcp, same bearer token, same input.

List Meta's current Facebook Messenger Platform features and Chirply's exact implementation state for each one, including supported controls, permission-gated products, Meta previews, policy limits, known build gaps, and retired legacy features. This is read-only and sends no message.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_capabilities \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "area": "messages"
  }'

Over MCP the same operation is the tool meta_messenger_capabilities at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately applies Meta's ban_user moderation action to one real Page-scoped Messenger person on one connected Facebook Page. This changes the live Page conversation and may prevent further interaction; it sends no message. Meta exposes no current moderation-state read, so verify the intended person and Page before confirming.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_conversation_ban \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "confirm": true
  }'

Over MCP the same operation is the tool meta_messenger_conversation_ban at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately applies Meta's block_user moderation action to one real Page-scoped Messenger person on one connected Facebook Page. This changes the live Page conversation and may prevent further interaction; it sends no message. Meta exposes no current moderation-state read, so verify the intended person and Page before confirming.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_conversation_block \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "confirm": true
  }'

Over MCP the same operation is the tool meta_messenger_conversation_block at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately assigns one real Page-owned Messenger custom label to one known Page-scoped person in Meta. This changes shared inbox organization but sends no message.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_conversation_label_assign \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "label_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_conversation_label_assign at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately removes one real Page-owned Messenger custom label from one known Page-scoped person in Meta. This changes shared inbox organization but sends no message.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_conversation_label_remove \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "label_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_conversation_label_remove at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the live custom labels attached to one Page-scoped Messenger person on one connected Facebook Page. This changes nothing and sends no message.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_conversation_labels_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example"
  }'

Over MCP the same operation is the tool meta_messenger_conversation_labels_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately applies Meta's move_to_spam action to one real Page-scoped Messenger person's conversation, moving it to Spam in Meta Business Suite Inbox. This changes a live external inbox and sends no message. Meta documents no restore-from-spam action on this API, so confirm the intended person and Page first.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_conversation_move_to_spam \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "confirm": true
  }'

Over MCP the same operation is the tool meta_messenger_conversation_move_to_spam at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately applies Meta's unban_user moderation action to one real Page-scoped Messenger person on one connected Facebook Page. This changes the live Page conversation and may allow interaction again; it sends no message. Meta exposes no current moderation-state read, so verify the intended person and Page before confirming.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_conversation_unban \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "confirm": true
  }'

Over MCP the same operation is the tool meta_messenger_conversation_unban at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately applies Meta's unblock_user moderation action to one real Page-scoped Messenger person on one connected Facebook Page. This changes the live Page conversation and may allow interaction again; it sends no message. Meta exposes no current moderation-state read, so verify the intended person and Page before confirming.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_conversation_unblock \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "psid": "example",
    "confirm": true
  }'

Over MCP the same operation is the tool meta_messenger_conversation_unblock at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately creates a real Page-owned Messenger custom label in Meta. It sends no message, but the new label becomes available to every app and teammate managing that Page.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_custom_label_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example"
  }'

Over MCP the same operation is the tool meta_messenger_custom_label_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately deletes a real Page-owned Messenger custom label from Meta, removing it from every person who has it. This cannot be undone and sends no message.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_custom_label_delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "label_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_custom_label_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Read one Page-owned Messenger custom label after verifying that the label belongs to the connected Facebook Page. This changes nothing and sends no message.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_custom_label_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "label_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_custom_label_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the live custom-label catalog for one connected Facebook Page. This changes nothing and sends no message.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_custom_labels_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_custom_labels_list at https://app.chirply.io/api/mcp, same bearer token, same input.

SENDS A REAL FACEBOOK MESSENGER HUMAN_AGENT REPLY. This is only for a literal support reply written and approved by a real person within seven days of that person's last Page message; it pauses automation on the conversation, reaches the recipient immediately with no undo, and must never carry automated, unrelated, or marketing content. Chirply requires an explicit human-authored attestation, while Meta separately requires HUMAN_AGENT App Review approval.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_human_agent_send \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "conversation_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "text": "example",
    "human_authored": true
  }'

Over MCP the same operation is the tool meta_messenger_human_agent_send at https://app.chirply.io/api/mcp, same bearer token, same input.

Derive Meta's Page-specific Login Connect login_id on Chirply's server and attach the website's authenticated app-scoped user id to one CRM contact. This stores no PSID and sends no message; the identity remains unable to send until Meta's signed user_messenger_contact opt-in webhook is captured.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_login_connect_identity_prepare \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "contact_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "asid": "example"
  }'

Over MCP the same operation is the tool meta_messenger_login_connect_identity_prepare at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately sends one real Facebook Messenger message to the CRM contact through Meta recipient.login_id. Chirply requires a signed user_messenger_contact opt-in for the same Page and contact, enforces Meta's 24-hour first-message deadline, records the consent basis, and permanently fences duplicate or indeterminate sends.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_login_connect_initial_message_send \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "contact_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "text": "example",
    "consent_basis": "example"
  }'

Over MCP the same operation is the tool meta_messenger_login_connect_initial_message_send at https://app.chirply.io/api/mcp, same bearer token, same input.

Attach a previously captured, signed messaging_optins.login_id webhook to one authenticated CRM contact through Chirply's opaque identity handle. Meta's login_id remains server-only; this does not accept an unverified opt-in, does not create a PSID, and sends no message.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_login_connect_optin_attach \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "contact_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_login_connect_optin_attach at https://app.chirply.io/api/mcp, same bearer token, same input.

Generate Meta's documented Login Connect OAuth URL and JavaScript SDK call for a connected Facebook Page. This returns setup code only; it creates no Meta object, sends no message, never exposes the server-only Meta client token, and cannot replace App Review or the manual App Dashboard Page toggle.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_login_connect_setup_generate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "redirect_uri": "https://example.com",
    "state": "example"
  }'

Over MCP the same operation is the tool meta_messenger_login_connect_setup_generate at https://app.chirply.io/api/mcp, same bearer token, same input.

Check the connected Page, pages_messaging grant, Page messaging task, messaging_optins webhook subscription, and Chirply server configuration for Meta Login Connect with Messenger. Meta exposes no API for App Review or its Login Connect App Dashboard toggle, so those remain explicitly manual; this sends no message.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_login_connect_status_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_login_connect_status_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a real external Meta Custom Audience dedicated to Messenger Marketing Messages for one Page and ad account. This requires a non-expiring Flow 1/3 system-business access token and changes external ad-account configuration, but uploads no customer data, sends no message, and spends nothing.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_audience_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example",
    "description": "example"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_audience_create at https://app.chirply.io/api/mcp, same bearer token, same input.

UNSUBSCRIBE REAL PEOPLE FROM THIS PAGE'S ENTIRE MESSENGER MARKETING MESSAGES AUDIENCE using Meta's current Page-level unsubscribe API. Each row must use phone/email, PSID, or an opaque subscriber handle; this ends Page-level marketing eligibility rather than merely removing one Custom Audience membership. It sends no Messenger message and spends nothing, but the person must opt in again before another paid Marketing Message.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_audience_unsubscribe \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "rows": [
      {}
    ],
    "unsubscribe_confirmed": true
  }'

Over MCP the same operation is the tool meta_messenger_marketing_audience_unsubscribe at https://app.chirply.io/api/mcp, same bearer token, same input.

UPLOAD CUSTOMER IDENTIFIERS TO META for matching into one real Messenger Marketing Custom Audience. Chirply normalizes and SHA-256 hashes every email/phone before transmission, sends at most 10,000 rows per confirmed request, and Meta may take up to 24 hours to match them; only matched people with valid marketing consent should be included, and subscription tokens remain hidden until Meta's 100-match privacy threshold is met. This sends no Messenger message and creates no paid delivery.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_audience_users_add \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "audience_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "rows": [
      {}
    ],
    "customer_data_rights_confirmed": true,
    "marketing_consent_confirmed": true,
    "upload_confirmed": true
  }'

Over MCP the same operation is the tool meta_messenger_marketing_audience_users_add at https://app.chirply.io/api/mcp, same bearer token, same input.

REMOVE SHA-256-HASHED CUSTOMER IDENTIFIERS FROM ONE REAL META CUSTOM AUDIENCE. This changes external audience membership after a confirmed request, but does not unsubscribe the people at Page level or remove them from other audiences; call the Page-level unsubscribe operation when marketing permission itself must end. It sends no Messenger message and spends nothing.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_audience_users_remove \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "audience_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "rows": [
      {}
    ],
    "removal_confirmed": true
  }'

Over MCP the same operation is the tool meta_messenger_marketing_audience_users_remove at https://app.chirply.io/api/mcp, same bearer token, same input.

List the live Messenger Marketing Messages Custom Audiences for one connected Page and ad account using Meta's exact subtype-1010 filter. This requires a non-expiring Flow 1/3 system-business access token; it sends nothing, uploads no customer data, and spends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_audiences_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_audiences_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a real paid Marketing Messages campaign for one connected Facebook Page and billed Meta ad account. Creating it does not send a message or create a charge, but it creates external ad infrastructure and establishes a real daily, lifetime, or Meta-estimated spend cap; the campaign remains inert until explicitly resumed and the send API is called.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_campaign_create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_campaign_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete one real direct Marketing Message campaign after proving its connected Page and billed ad-account ownership. This cannot be undone, removes external campaign history/configuration, and does not recall messages already delivered.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_campaign_delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_campaign_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Read one live direct Marketing Message campaign after proving its Page and billed ad-account ownership, including all three Meta delivery objects, budget, schedule, status, and Pixel attribution. This sends nothing and spends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_campaign_get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_campaign_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Pause the real message, message set, and campaign behind one direct Messenger Marketing campaign, stopping future paid sends from being accepted. This changes external Meta state but does not recall messages already delivered.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_campaign_pause \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_campaign_pause at https://app.chirply.io/api/mcp, same bearer token, same input.

Activate the real campaign, message set, and message behind one direct Messenger Marketing campaign. Activation does not itself send, but it enables later approved sends that message real subscribers and charge the billed ad account; Meta requires about 10 minutes after activation before sending.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_campaign_resume \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_campaign_resume at https://app.chirply.io/api/mcp, same bearer token, same input.

Update the name, same-mode budget, or schedule of a real direct Marketing Message campaign after proving its Page and ad-account ownership. This changes external paid-campaign configuration and can raise how much a later approved send may spend, but it does not itself send a message; Meta does not document switching a live campaign between daily and lifetime budget modes, so Chirply refuses that guess.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_campaign_update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_campaign_update at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the live direct Marketing Message campaigns owned by one connected Facebook Page and billed through one connected Meta ad account, including the underlying campaign, message-set, and message statuses, budget, schedule, and Pixel attribution. This sends nothing and spends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_campaigns_list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_campaigns_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Ask Meta for the estimated lower and upper number of paid Messenger Marketing send calls supported by one daily or lifetime budget for a connected Page/ad account. This is an estimate, not a guarantee; it sends nothing, changes no budget, and incurs no delivery charge.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_delivery_estimate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_delivery_estimate at https://app.chirply.io/api/mcp, same bearer token, same input.

Read Meta's live paid Messenger Marketing delivered count, reads, link clicks, spend, cost per delivery/click, and attributed Pixel or Conversions API actions, values, and purchase ROAS for one Page-owned campaign. Metrics may be estimated or region-excluded exactly as Meta documents; this sends nothing and spends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_insights \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "campaign_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool meta_messenger_marketing_insights at https://app.chirply.io/api/mcp, same bearer token, same input.

SEND A REAL IN-THREAD FACEBOOK MESSENGER OPT-IN REQUEST to a person who recently started a Page conversation. The notification_messages template asks for explicit Marketing Messages consent; it does not itself grant consent, spend paid-delivery budget, or authorize a later send until Meta returns a subscription token. Chirply enforces the current 24-hour thread window and writes a durable receipt first.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/meta.messenger_marketing_optin_request \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "conversation_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "title": "Example",
    "payload": "example",
    "request_key": "example",
    "consent_request_confirmed": true
  }'

Over MCP the same operation is the tool meta_messenger_marketing_optin_request at https://app.chirply.io/api/mcp, same bearer token, same input.

Ask Meta to render a safe hosted preview for one documented rich Marketing Message against a connected Page and ad account. This sends nothing to a subscriber, changes no campaign, and incurs no delivery charge; Chirply returns only Meta's verified facebook.com preview URL, never executable iframe HTML.

Parameters