Skip to main content
Glama

meta_ads_creatives_create

Create a single-image Meta Ads ad creative by providing a destination URL, Facebook Page, and image (URL or hash). Optionally add headline, body text, and call-to-action. Returns the creative ID and object story ID for use in ad sets.

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?

No annotations exist, so description carries full burden. Discloses mutation, rollback soft-delete, and image source behavior (fetch vs. hash). Could mention post-creation state (active/paused) or auth requirements, but overall covers main behavioral traits.

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 dense sentences cover purpose, return values, behavior, image source choices, rollback, and sibling differentiation. No filler; every sentence adds value.

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, mutation, rollback, image options, and sibling tools. Missing post-creation state and default behaviors, but given the output schema absence, return values are mentioned. For a 10-param tool with no output schema, it is fairly complete.

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. The tool description adds value by explaining the mutual exclusivity of image_url and image_hash, and the fetch-vs-hash tradeoff. Provides context around account_id fallback and valid CTA enum, though schema already covers these.

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 'Creates a single-image Meta Ads AdCreative' and specifies return values (id, object_story_id). It distinguishes itself from sibling tools (carousel, dynamic) by naming them explicitly.

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 when-to-use guidance: 'Supply exactly one of image_url or image_hash' with reasoning. Also advises alternatives: 'For multi-image carousels use meta_ads_creatives_create_carousel; for dynamic / automatic optimization use meta_ads_creatives_create_dynamic.' Mentions rollback for reversal.

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