Skip to main content
Glama

meta_ads_creatives_create

Create a single image or video Meta Ads ad creative, returning the new creative ID and object story ID. Videos require a thumbnail and call-to-action.

Instructions

Creates a single image or video Meta Ads AdCreative. Returns the new creative's id and object_story_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Image mode: 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. Video mode: supply video_id plus exactly one of video_thumbnail_image_hash / video_thumbnail_image_url — Meta requires a thumbnail on every video creative. The video must already be fully processed: poll meta_ads_videos_get until status.video_status reports ready (typically a few minutes after upload), and pick a thumbnail via meta_ads_videos_thumbnails. Video and image parameters are mutually exclusive. Video mode also REQUIRES call_to_action: Meta's video_data has no link field, so the destination is carried inside the CTA and a video creative without one is rejected. 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
nameYesCreative name shown in Ads Manager. Internal label — not visible to end users.
messageNoPrimary ad body text shown above the image or video. Plain text, emoji allowed. Meta recommends ≤125 characters to avoid truncation on mobile.
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.
headlineNoHeadline shown below the media. ~40 characters fits most placements without truncation. Maps to link_data.name in image mode and video_data.title in video mode.
link_urlYesDestination URL the ad links to when tapped. Must be HTTPS and domain-verified on the ad account.
video_idNoPre-uploaded video ID from meta_ads_videos_upload / meta_ads_videos_upload_file. Switches the creative to video mode (object_story_spec.video_data). The video must be fully processed first — poll meta_ads_videos_get. Mutually exclusive with image_url / image_hash. Setting it makes two otherwise-optional parameters mandatory: one of the video_thumbnail_image_* parameters, and call_to_action.
image_urlNoPublic HTTPS image URL. Meta fetches and hosts the asset. Mutually exclusive with image_hash — supply exactly one of them.
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.
image_hashNoImage hash returned from meta_ads_creatives_upload_image / meta_ads_images_upload_file. Mutually exclusive with image_url.
descriptionNoDescription / link-caption text shown below the headline. Optional; not all placements render it. Maps to link_data.description in image mode and video_data.link_description in video mode.
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. REQUIRED when video_id is set: the destination link is carried inside this button (video_data.call_to_action.value.link) because Meta's video_data has no link field of its own. link_url is filled in there automatically — pass only the button label.
video_thumbnail_image_urlNoThumbnail image URL for the video creative — typically a uri from meta_ads_videos_thumbnails (prefer the entry flagged is_preferred). Requires video_id; mutually exclusive with video_thumbnail_image_hash.
video_thumbnail_image_hashNoThumbnail image hash for the video creative, from meta_ads_creatives_upload_image / meta_ads_images_upload_file. Requires video_id; mutually exclusive with video_thumbnail_image_url.
Behavior5/5

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

With no annotations, the description fully carries the burden. It discloses that the tool is mutating, not automatically reversible, and recommends recording before-state via mureo_state_action_log_append. It also explains the return values, Meta's image hosting behavior, mandatory thumbnail for video, video processing requirements, and the CTA requirement.

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 efficiently structured: purpose first, then return values, mutating warning, mode-specific instructions, and finally sibling tool alternatives. Every sentence adds value with no redundancy or fluff, keeping the length appropriate for the tool's 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 the tool's complexity (13 params, two modes, mutual exclusions, prerequisites, and rollback concerns), the description is remarkably complete. It covers prerequisites, return values, mutating nature, parameter relationships, and when to use alternatives—all without needing an output schema.

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 coverage is 100%, but the description adds substantial meaning beyond the schema: explaining image_url vs image_hash semantics, mutual exclusivity of video/image parameters, the requirement for call_to_action in video mode, and the thumbnail preconditions. This dramatically improves parameter understanding.

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 opens with a specific verb+resource: 'Creates a single image or video Meta Ads AdCreative.' It clearly distinguishes from siblings by naming meta_ads_creatives_create_carousel and meta_ads_creatives_create_dynamic as alternatives for other use cases.

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?

It provides explicit when-to-use guidance: image mode vs video mode, which parameters to supply in each, prerequisites like video processing and thumbnail selection, and directs carousel/dynamic use cases to alternative tools. This is comprehensive context for selecting and invoking the tool correctly.

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