freedom-mcp

Create Meta ad draft

create_meta_ad_draft

Destructive

Create a complete Meta (Facebook/Instagram) ad draft — campaign + ad set + creative + ad — ALL in PAUSED state, spending nothing. Draft primary_text via draft_ad_variants first (paid-ad genre, operator picks a variant) unless the operator supplied their own copy. Use when the user wants to set up or draft an ad. Activation is a separate human-approved step (set_meta_ad_status).

Routing: Meta ad setup → if ad copy is not already picked, run draft_ad_variants (channel meta) first; then create here with the picked primary_text + cta and its hook tag in campaign_name

[sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time. Call it on the first clear ask; the card is the yes — do not re-ask in chat.]

Input Schema

TableJSON Schema

Name	Required	Description
`cta`	No	Optional call-to-action: LEARN_MORE, SIGN_UP, GET_STARTED, CONTACT_US, DOWNLOAD, SUBSCRIBE
`link_url`	Yes	https destination URL (landing page, with UTMs)
`companyId`	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`objective`	No	OUTCOME_TRAFFIC (default) \| OUTCOME_AWARENESS \| OUTCOME_ENGAGEMENT \| OUTCOME_LEADS (needs firing pixel) \| OUTCOME_SALES (needs firing pixel)
`targeting`	No	Audience: {countries: ["US"], age_min, age_max, interests: [{id, name}]}
`daily_budget`	Yes	Daily budget in the account currency, major units (e.g. 25 = 25 USD/day)
`primary_text`	Yes	The ad copy (primary text)
`ad_account_id`	No	Ad account (act_<digits>). Optional when the connection has exactly one.
`campaign_name`	Yes	Campaign name, e.g. "PCAI cold traffic — Compliance Crusader v1"
`conversion_event`	No	Website event to optimize: OUTCOME_LEADS supports LEAD (default) or COMPLETE_REGISTRATION (completed signup); OUTCOME_SALES supports PURCHASE (default). Omit for other objectives. Use COMPLETE_REGISTRATION when browser/CAPI sends CompleteRegistration.
`image_artifact_id`	No	Optional agent_artifacts image id for the creative

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / conversion_event

Added value: +{
+  "description": "Website event to optimize: OUTCOME_LEADS supports LEAD (default) or COMPLETE_REGISTRATION (completed signup); OUTCOME_SALES supports PURCHASE (default). Omit for other objectives. Use COMPLETE_REGISTRATION when browser/CAPI sends CompleteRegistration.",
+  "enum": [
+    "LEAD",
+    "COMPLETE_REGISTRATION",
+    "PURCHASE"
+  ],
+  "type": "string"
+}

changedInput schema / properties / objective / description

Previous value: -"OUTCOME_TRAFFIC (default) | OUTCOME_AWARENESS | OUTCOME_ENGAGEMENT"New value: +"OUTCOME_TRAFFIC (default) | OUTCOME_AWARENESS | OUTCOME_ENGAGEMENT | OUTCOME_LEADS (needs firing pixel) | OUTCOME_SALES (needs firing pixel)"

First observedJul 19, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses that everything is created in a paused state spending nothing, that primary_text must come from draft_ad_variants or operator-supplied copy, and that activation is a separate human-approved step. It also encodes the sensitive-tier approval behavior, which is valuable context the structured fields don't carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior is front-loaded in the first sentence, and the routing and approval sections are compact and non-redundant. Every paragraph provides decision-relevant information: what is created, what to run first, and when approval is needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 11-parameter tool with nested objects and no output schema, the description covers when to call, what gets created, prerequisite copy generation, activation separation, and approval handling. Very little is left for an agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description still adds meaning for primary_text, cta, and campaign_name by explaining that copy should be picked from draft_ad_variants and that the hook tag belongs in campaign_name. It doesn't add per-parameter detail for all 11 fields, but the schema already covers those well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource: 'Create a complete Meta ad draft — campaign + ad set + creative + ad — ALL in PAUSED state.' It clearly distinguishes itself from draft_ad_variants and set_meta_ad_status, so an agent can tell what this tool does and does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use when the user wants to set up or draft an ad' and gives an explicit routing rule: run draft_ad_variants first if copy isn't already picked, then create here. It also names set_meta_ad_status as the separate activation step and calls out the operator-copy exception, giving clear when-to-use vs. alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All freedom-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?