freedom-mcp

Create X ad draft

create_x_ad_draft

Destructive

Create an X (Twitter) ads draft — campaign + line item + optional ad creative — ALL in PAUSED state, spending nothing. Pass ad_text to mint a nullcast ad post (promoted-only, never shows on the timeline organically) attached to the paused line item, or post_id to promote an existing post. Draft ad_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 X ad. Activation is a separate human-approved step (set_x_ad_status). Distinct from create_meta_ad_draft.

Routing: X ad setup → if ad copy is not already picked, run draft_ad_variants (channel x) first; then create here with the picked text + 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
`bid`	No	Optional bid in major units (default 1)
`ad_text`	No	Ad copy (≤280 chars) — mints a nullcast ad post and attaches it to the paused line item. Mutually exclusive with post_id.
`country`	No	ISO-2 country for location targeting, default US
`post_id`	No	Existing X post id to promote on the paused line item instead of minting new copy.
`companyId`	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`objective`	No	Line-item objective, default WEBSITE_CLICKS
`daily_budget`	Yes	Daily budget in the account currency, major units (e.g. 25 = 25 USD/day)
`ad_account_id`	No	Ads account id. Optional when the connection has exactly one.
`campaign_name`	Yes	Campaign name, e.g. "PCAI cold traffic v1"
`funding_instrument_id`	No	Payment method id. Optional when the account has exactly one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / ad_text

Added value: +{
+  "description": "Ad copy (≤280 chars) — mints a nullcast ad post and attaches it to the paused line item. Mutually exclusive with post_id.",
+  "type": "string"
+}

addedInput schema / properties / post_id

Added value: +{
+  "description": "Existing X post id to promote on the paused line item instead of minting new copy.",
+  "type": "string"
+}

AddedAug 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations indicate destructiveHint=true, but description adds meaningful safety context: 'ALL in PAUSED state, spending nothing' and that activation is a separate human-approved step. Also explains nullcast posts are promoted-only, never on timeline. This goes beyond annotations in disclosing behavior and side effects.

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

Conciseness4/5

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

The description is long but dense. It front-loads the core behavior and constraints, then provides routing and approval details. A few sentences could be tightened (e.g., the sensitive-tier block is somewhat rambling), but overall each part contributes to correct usage.

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?

Given 10 parameters, no output schema, and a complex workflow, the description covers all necessary aspects: safety (paused, no spend), copy workflow (draft_ad_variants), differentiation from platform-sibling, and approval requirements. An agent has enough to call it correctly.

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 parameter descriptions exist. The tool description adds value by explaining the relationship between ad_text and post_id (mutually exclusive), and that ad_text mints a nullcast post while post_id promotes existing post. It also notes default values indirectly (e.g., 'default 1' is in schema, but the description contextualizes them).

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?

States a specific verb ('Create') and resource ('X ads draft') with key constraints (campaign + line item + optional ad creative, ALL in PAUSED state, spending nothing). Explicitly distinguishes from create_meta_ad_draft. The 'Distinct from create_meta_ad_draft' line differentiates it from a sibling tool.

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?

Provides explicit routing: run draft_ad_variants first if ad copy not already picked, then create here. States intended use: 'Use when the user wants to set up or draft an X ad.' Also mentions activation is separate (set_x_ad_status), giving a when-not/alternative.

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?