Skip to main content
Glama

meta_ads_creatives_create

Create a single-image Meta Ads ad creative by providing ad name, page, link, and image (URL or hash). Returns the creative ID for use in campaigns.

Instructions

Creates a single-image 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. 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
nameYesCreative name shown in Ads Manager. Internal label — not visible to end users.
messageNoPrimary ad body text shown above the image. 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 image. ~40 characters fits most placements without truncation.
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.
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.
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.
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 declares mutability, warns about non-reversibility, and advises using mureo_state_action_log_append for rollback. It explains how image_url triggers fetching versus image_hash, covering important behavioral differences.

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?

Concise but thorough: opens with core action and return, then mutation warning, then image inputs, then alternatives. Every sentence adds distinct value; no redundancy or filler.

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?

Despite no output schema, return values are specified. Prerequisites (account_id format, image_hash source) covered. Alternative tools and their distinctions are mentioned. The description is self-contained for a tool with 10 parameters and 100% schema coverage.

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%, so baseline is 3. Description adds beyond: explains account_id fallback behavior, mutual exclusivity of image_url/image_hash with nuance of Meta's fetch logic, and notes CTA validity depends on campaign objective. This extra context justifies a score above baseline.

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?

Description clearly states it creates a single-image Meta Ads AdCreative and returns the new creative's id and object_story_id. It distinctly separates from carousel and dynamic variants by naming sibling tools, leaving no ambiguity.

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?

Explicitly tells when to use (single-image creatives) and when not to (carousels or dynamic). Provides specific alternative tool names and mentions prerequisite of uploading image before using image_hash, giving clear 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/logly/mureo'

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