Adsap

Create Ad

adsap_create_ad

Create a Meta ad (image/video) in an ad set. Defaults to PAUSED. Creative: pass exactly ONE of creative_spec.feed_creative_name (library file), image_hash / video_id (reuse an existing Meta image/video with new copy), creative_id (reuse a WHOLE existing creative as-is) or object_story_id (run an existing Page post as the ad) — the last two keep the original post and its likes/comments, and need no copy fields. ALWAYS call with dry_run: true first: it validates and renders a launch review card where the user confirms, creates (paused) and activates in-card — after it renders, reply with ONE short sentence and stop; do not call the real create from chat unless the user explicitly asks in a new message and the card's activity log shows nothing was created there. For App promotion (OUTCOME_APP_PROMOTION) ad sets: set link_url to the app's store URL (same as the ad set's promoted_object.object_store_url) and call_to_action to INSTALL_MOBILE_APP (or USE_MOBILE_APP/DOWNLOAD); the promoted app binding comes from the ad set.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`status`	No
`dry_run`	No	Validate only, no creation
`ad_format`	Yes
`ad_set_id`	Yes
`ad_account_id`	Yes
`creative_spec`	Yes
`idempotency_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 25, 2026

addedInput schema / properties / creative_spec / properties / creative_id

Added value: +{
+  "description": "Reuse a WHOLE existing adcreative as-is (id from adsap_get_ad's creative_id or adsap_list_ads). The new ad shows the exact same content AND keeps the underlying post with its likes/comments (social proof). Copy fields (primary_texts, headlines, call_to_action, link_url, page_id) are not used — the creative already contains them. Exactly ONE creative pointer per call.",
+  "type": "string"
+}

addedInput schema / properties / creative_spec / properties / headlines / description

Added value: +"1-5 headlines. REQUIRED when building a new creative; not used when reusing creative_id / object_story_id."

addedInput schema / properties / creative_spec / properties / object_story_id

Added value: +{
+  "description": "Reuse an existing Facebook Page post as the ad, form <page_id>_<post_id> (from adsap_get_ad's object_story_id / effective_object_story_id). Keeps the post and its social proof. Copy fields are not used. Exactly ONE creative pointer per call.",
+  "type": "string"
+}

addedInput schema / properties / creative_spec / properties / page_id / description

Added value: +"Facebook Page id. REQUIRED when building a new creative (feed_creative_name / image_hash / video_id); not needed when reusing creative_id / object_story_id — the identity comes from the reused creative."

removedInput schema / properties / creative_spec / properties / page_id / minLength
```
Removed value: -1
```

addedInput schema / properties / creative_spec / properties / primary_texts / description

Added value: +"1-5 primary texts. REQUIRED when building a new creative; not used when reusing creative_id / object_story_id."

removedInput schema / properties / creative_spec / required

Removed value: -[
-  "page_id",
-  "primary_texts",
-  "headlines",
-  "call_to_action"
-]

Changed5 schema fields changedSep 25, 2026

changedInput schema / properties / creative_spec / properties / feed_creative_name / description

Previous value: -"Feed creative filename (1080x1080). Must exist in creative_metadata table."New value: +"Feed creative filename (1080x1080) from the ADSAP creative library (adsap_list_creative_assets). Pass exactly ONE of feed_creative_name, image_hash or video_id."

removedInput schema / properties / creative_spec / properties / feed_creative_name / minLength
```
Removed value: -1
```

addedInput schema / properties / creative_spec / properties / image_hash

Added value: +{
+  "description": "Reuse an EXISTING Meta image by its image hash (e.g. from adsap_get_ad's creative_summary.images, to build a new ad with the same image). SINGLE_IMAGE only. The image must be in the ADSAP creative library — if it is not found, run adsap_import_account_creatives once (imports the account's full existing image/video library) and retry. Pass exactly ONE of feed_creative_name, image_hash or video_id.",
+  "type": "string"
+}

addedInput schema / properties / creative_spec / properties / video_id

Added value: +{
+  "description": "Reuse an EXISTING Meta video by its video id (e.g. from adsap_get_ad's creative_summary.videos). SINGLE_VIDEO only. The video must be in the ADSAP creative library — if it is not found, run adsap_import_account_creatives once and retry. Pass exactly ONE of feed_creative_name, image_hash or video_id.",
+  "type": "string"
+}

changedInput schema / properties / creative_spec / required

Previous value: -[
-  "page_id",
-  "feed_creative_name",
-  "primary_texts",
-  "headlines",
-  "call_to_action"
-]New value: +[
+  "page_id",
+  "primary_texts",
+  "headlines",
+  "call_to_action"
+]

Changed1 schema field changedSep 19, 2026

addedInput schema / properties / creative_spec / properties / leadgen_form_id / description

Added value: +"Id of the Instant Form of a lead ad, from adsap_manage_instant_form or adsap_list_meta_assets (asset_type instant_forms). The form must belong to the same Facebook Page as the ad."

First observedSep 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers: it states the PAUSED default, the dry_run validation-and-render workflow, that the card creates (paused) and activates in-card, that creative_id/object_story_id reuse preserve the original post and its likes/comments, and the app-promotion binding constraint. This is exemplary disclosure of side effects and controlled execution for a mutation tool.

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 every sentence carries operational weight — critical workflow steps (dry_run first, stop after one sentence) are front-loaded after the purpose. The app-promotion addendum is niche but necessary for a common ad type. Nothing is padding; the density is justified by the tool's real complexity.

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 tool with 8 parameters, nested creative_spec object, no annotations, and no output schema, this is remarkably complete. It covers the creation workflow, the validation path, the creative selection constraints, defaults, cross-references to prerequisite/companion tools (adsap_import_account_creatives, adsap_list_creative_assets), and error-recovery steps (retry after import). No essential operational detail is missing.

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?

At 13% schema description coverage, the description must compensate, and it does significantly. It explains the creative_spec selection rule ('pass exactly ONE of...'), the meaning of each pointer type (library file vs. reuse-existing-with-new-copy vs. reuse-whole-creative vs. page-post), the dry_run semantic, and the app-promotion link_url/call_to_action requirement. Combined with the schema's own rich per-field descriptions in creative_spec, parameter meaning is well covered.

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 — 'Create a Meta ad (image/video) in an ad set' — states a specific verb, resource, and scope. It distinguishes this tool from the sibling create tools (create_campaign, create_ad_sets, create_ad_from_ig_post) by specifying the ad-in-ad-set level and format, leaving no ambiguity about what entity is created.

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

Usage Guidelines4/5

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

The description gives explicit when/when-not guidance: 'ALWAYS call with dry_run: true first', 'do not call the real create from chat unless the user explicitly asks in a new message', and the rule to stop after one sentence once the card renders. It also explains the mutually-exclusive creative pointer options. It doesn't explicitly route to sibling alternatives (e.g., when to prefer create_ad_from_ig_post), but the in-tool conditional workflow is exceptionally clear.

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

All Adsap 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?