Skip to main content
Glama

create_ad_creative

Generate a creative ID for a single-image ad by supplying image, link, and copy, enabling ad creation or update via returned ID.

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
Behavior4/5

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

With no annotations, the description carries full burden. It discloses auto-resolution of Instagram identity and fallback to Facebook-only, plus naming enforcement. It lacks details on rate limits or idempotency but is generally transparent.

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?

Well-structured: purpose, return value, requirements, limitations, then parameter list. Every sentence is informative without redundancy. Length is appropriate for the 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?

Given 9 parameters with 0% schema coverage and no output schema, the description covers all inputs and explains the output (creative_id). It addresses constraints (single-image only) and integration with other tools.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates. It explains each parameter in detail (e.g., account_id format, image_hash origin, valid CTA types) and adds context beyond the schema titles.

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 description explicitly states 'Create a standalone single-image ad creative' and identifies the resource and type. It mentions the return value (creative_id) and distinguishes from create_multi_asset_ad for video/carousel/dynamic creatives.

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?

Clearly specifies when to use this tool (single-image creatives) and provides the alternative create_multi_asset_ad for other types. It lists requirements like Facebook Page ID but does not explicitly state when not to use beyond that alternative.

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