Skip to main content
Glama

create_ad_creative

Create a single-image ad creative by supplying account, page, image, URL, and text. Returns a creative ID for building or updating ads.

Instructions

Create a standalone single-image ad creative.

Returns creative_id for use in ad creation (create_ad_from_manifest) or ad update (update_ad creative swap).

Requires a Facebook Page ID. Instagram identity is auto-resolved from the page - if unavailable, creative is created for Facebook only.

Single-image creatives only in v1. For video, carousel, or dynamic creatives, use create_multi_asset_ad.

Args: account_id: Ad account ID (e.g., 'act_123456789'). page_id: Facebook Page ID for the creative. image_hash: Image hash from upload_ad_image. link_url: CTA destination URL. primary_text: Main ad copy text (the "message"). headline: Optional headline (appears below image). description: Optional description text. cta_type: Call-to-action type. Default 'LEARN_MORE'. Valid: LEARN_MORE, SHOP_NOW, SIGN_UP, SUBSCRIBE, CONTACT_US, GET_OFFER, BOOK_TRAVEL, DOWNLOAD, APPLY_NOW, WATCH_MORE, GET_QUOTE, SEND_MESSAGE, ORDER_NOW, NO_BUTTON. name: Optional creative name. Subject to naming enforcement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
page_idYes
image_hashYes
link_urlYes
primary_textYes
headlineNo
descriptionNo
cta_typeNoLEARN_MORE
nameNo
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses return of creative_id, auto-resolution of Instagram, limitation to single-image, and naming enforcement. Does not cover idempotency, rate limits, permissions, or error handling. Adequate but not exhaustive.

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?

Two concise paragraphs plus arg list. Front-loaded with purpose and key constraints. Every sentence adds value. No redundancy or fluff.

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

Completeness4/5

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

Covers purpose, usage guidelines, parameter semantics, and key behavioral constraints. Given no output schema and no annotations, description is quite complete. Could mention error handling or validation but overall sufficient.

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 0%, but description adds meaning for all 9 parameters: explains each required and optional argument, lists valid CTA values, and mentions naming enforcement. Adds significant value beyond schema names.

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?

Clearly states verb 'Create' and resource 'standalone single-image ad creative'. Distinguishes from sibling create_multi_asset_ad for video/carousel/dynamic. Mentions return value (creative_id) and integration points.

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?

Explicitly states this tool is for single-image creatives only and directs to create_multi_asset_ad for other formats. Mentions prerequisite (Facebook Page ID) and auto-resolution of Instagram identity. Lacks explicit 'when not to use' but provides sufficient context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brandu-mos/konquest-meta-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server