meta-ads-mcp

get_ad_creative_by_id

Retrieve detailed information about a specific Facebook ad creative by its ID, including status, specs, metrics, and associated assets like images, videos, and pages.

Instructions

Retrieves detailed information about a specific Facebook ad creative.

This tool interfaces with the Facebook Graph API to fetch comprehensive details about an ad creative, such as its name, status, specifications, engagement metrics, and associated objects (like images, videos, and pages).

Args: creative_id (str): The ID of the ad creative to retrieve. fields (Optional[List[str]]): A list of specific fields to retrieve. If None, returns the default set of fields. Available fields include (but are not limited to): - 'account_id': Ad account ID the creative belongs to - 'actor_id': ID of the Facebook actor (page/app/person) associated with this creative - 'adlabels': Ad labels associated with this creative - 'applink_treatment': App link treatment type - 'asset_feed_spec': Specifications for dynamic ad creatives - 'authorization_category': For political ads, shows authorization category - 'body': Ad body text content - 'branded_content_sponsor_page_id': ID of the sponsor page for branded content - 'call_to_action_type': Type of call to action button - 'effective_authorization_category': Effective authorization category for the ad - 'effective_instagram_media_id': Instagram media ID used in the ad - 'effective_instagram_story_id': Instagram story ID used in the ad - 'effective_object_story_id': Object story ID used for the ad - 'id': Creative ID - 'image_hash': Hash of the image used in the creative - 'image_url': URL of the image used - 'instagram_actor_id': Instagram actor ID associated with creative (deprecated) - 'instagram_permalink_url': Instagram permalink URL - 'instagram_story_id': Instagram story ID - 'instagram_user_id': Instagram user ID associated with creative - 'link_og_id': Open Graph ID for the link - 'link_url': URL being advertised - 'name': Name of the creative in the ad account library - 'object_id': ID of the Facebook object being advertised - 'object_story_id': ID of the page post used in the ad - 'object_story_spec': Specification for the page post to create for the ad - 'object_type': Type of the object being advertised - 'object_url': URL of the object being advertised - 'platform_customizations': Custom specifications for different platforms - 'product_set_id': ID of the product set for product ads - 'status': Status of this creative (ACTIVE, IN_PROCESS, WITH_ISSUES, DELETED) - 'template_url': URL of the template used - 'thumbnail_url': URL of the creative thumbnail - 'title': Ad headline/title text - 'url_tags': URL tags appended to landing pages for tracking - 'use_page_actor_override': Use the page actor instead of ad account actor - 'video_id': ID of the video used in the ad

thumbnail_width (Optional[int]): Width of the thumbnail in pixels. Default: 64.
thumbnail_height (Optional[int]): Height of the thumbnail in pixels. Default: 64.

Returns: Dict: A dictionary containing the requested ad creative details.

Example: ```python # Get basic information about an ad creative creative = get_ad_creative_details( creative_id="23842312323312", fields=["name", "status", "object_story_id", "thumbnail_url"] )

# Get a larger thumbnail with specific dimensions
creative_with_thumbnail = get_ad_creative_details(
    creative_id="23842312323312", 
    fields=["name", "thumbnail_url"],
    thumbnail_width=300,
    thumbnail_height=200
)
```

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	No
`creative_id`	Yes
`thumbnail_width`	No
`thumbnail_height`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses that fields defaults to a standard set when None, that thumbnail dimensions default to 64x64, and that the result is a dictionary. It also makes the read-only nature clear through 'Retrieves' and 'fetch'. It does not discuss errors or rate limits, but those are less critical for a simple getter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but the length is justified by the need to document ~30 available field values when the schema itself doesn't. It is well-structured with a clear purpose statement, parameter docs, return type, and example. Minor issue: the example calls 'get_ad_creative_details' instead of the tool's actual name, which could cause slight confusion.

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?

For a tool with 4 parameters and no annotation coverage, the description covers everything needed to call it correctly: purpose, parameter semantics, available fields, defaults, return type, and a practical example. The output schema existence reduces the need to explain return structure further. Only explicit alternative routing is absent, which is a minor gap.

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?

The input schema provides only parameter names with no descriptions (0% coverage), so the description fully compensates. Each parameter is explained, fields includes an extensive list of valid values with meanings, thumbnail dimensions are defined, and defaults are stated. The example further clarifies real usage.

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 states a specific action ('Retrieves detailed information') and a specific resource ('a specific Facebook ad creative'). The 'by_id' naming plus required creative_id parameter clearly distinguishes it from sibling tools like get_ad_creatives_by_ad_id, which retrieve creatives by ad ID.

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 clearly implies this tool is for fetching a single ad creative when you have its creative_id, and lists exactly what information it returns. However, it does not explicitly call out alternatives or state when not to use this tool, so some inference is left to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server