Skip to main content
Glama

meta_ads_creatives_create

Create a single-image Meta Ads ad creative with customizable name, page, link, image, and text. Returns creative ID for immediate use.

Instructions

Creates a single-image Meta Ads AdCreative. Returns the new creative's id and object_story_id. Mutating, reversible via rollback_apply (rollback soft-deletes the creative). Supply exactly one of image_url or image_hash — image_url triggers Meta to fetch and host the image; image_hash references an image already uploaded via meta_ads_creatives_upload_image or meta_ads_images_upload_file. For multi-image carousels use meta_ads_creatives_create_carousel; for dynamic / automatic optimization use meta_ads_creatives_create_dynamic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
nameYesCreative name shown in Ads Manager. Internal label — not visible to end users.
page_idYesFacebook Page ID that the ad will be published as. Must be a page the authenticated user has permission to post from. Required by Meta for every creative — ads cannot run without a page identity.
link_urlYesDestination URL the ad links to when tapped. Must be HTTPS and domain-verified on the ad account.
image_urlNoPublic HTTPS image URL. Meta fetches and hosts the asset. Mutually exclusive with image_hash — supply exactly one of them.
image_hashNoImage hash returned from meta_ads_creatives_upload_image / meta_ads_images_upload_file. Mutually exclusive with image_url.
messageNoPrimary ad body text shown above the image. Plain text, emoji allowed. Meta recommends ≤125 characters to avoid truncation on mobile.
headlineNoHeadline shown below the image. ~40 characters fits most placements without truncation.
descriptionNoDescription / link-caption text shown below the headline. Optional; not all placements render it.
call_to_actionNoCall-to-action button label. Valid values include LEARN_MORE, SIGN_UP, SHOP_NOW, DOWNLOAD, CONTACT_US, SUBSCRIBE, GET_QUOTE, BOOK_TRAVEL, APPLY_NOW. Omit to render no button (link tap still works). The valid set depends on the parent campaign's objective.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool is mutating, reversible via rollback_apply which soft-deletes the creative. It explains the behavior of image_url (Meta fetches and hosts) vs image_hash (references uploaded image). This covers key behavioral aspects without contradictions.

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 description is five sentences, each essential: purpose, return values, mutation/reversibility, image parameter behavior, and sibling alternatives. No fluff or redundancy; information is front-loaded and well-organized.

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?

Given 10 parameters, no output schema, and no annotations, the description covers return values, image handling, sibling differentiation, and mutation/reversibility. It does not discuss error cases or detailed output format beyond id and object_story_id, but these are reasonable omissions for a creation tool.

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% with detailed descriptions, but the tool description adds significant value: it explains the mutual exclusivity of image_url and image_hash, the return values (id and object_story_id), and the image hosting behavior. This goes beyond what the schema alone provides.

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 clearly states the tool creates a single-image Meta Ads AdCreative and returns the creative's id and object_story_id. It distinguishes from siblings by explicitly naming alternatives for carousels and 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?

The description explains when to use this tool (single-image creatives) and when not (use meta_ads_creatives_create_carousel for carousels or meta_ads_creatives_create_dynamic for dynamic). It also clarifies the mutual exclusivity of image_url and image_hash. However, it could be more explicit about prerequisites like page permissions.

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/logly/mureo'

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