Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott

Get Meta Ad Creatives by Ad ID

meta_ads_get_ad_creatives_by_ad_id
Read-onlyIdempotent

Retrieve ad creatives for a specific ad ID, including fields like image URL and title, to analyze or optimize ad performance.

Instructions

Retrieve the ad creatives associated with a specific Meta ad.

Args:

  • ad_id (string): Ad ID to retrieve creatives for, e.g., '23843211234567'

  • fields (string[]): Fields to retrieve. Available: id, name, account_id, actor_id, adlabels, asset_feed_spec, authorization_category, body, call_to_action_type, effective_authorization_category, effective_instagram_media_id, effective_object_story_id, image_hash, image_url, instagram_permalink_url, instagram_story_id, instagram_user_id, link_url, object_id, object_story_id, object_story_spec, object_type, object_url, platform_customizations, product_set_id, status, template_url, thumbnail_url, title, url_tags, use_page_actor_override, video_id

  • limit (number): Maximum creatives per page (default: 25)

  • after / before (string): Pagination cursors from response.paging.cursors

  • date_format (string): Date format: 'U' for Unix timestamp, 'Y-m-d H:i:s' for MySQL datetime

Returns: Object with data (creative array) and paging. Use meta_ads_fetch_pagination_url with paging.next for more results.

Examples:

  • Use when: "What creatives are used by ad 23843211234567?"

  • Use when: "Get the image URLs and titles for all creatives on this ad"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYesAd ID to retrieve creatives for, e.g., '23843211234567'
fieldsNoFields to retrieve. Available: id, name, account_id, actor_id, adlabels, asset_feed_spec, authorization_category, body, call_to_action_type, effective_authorization_category, effective_instagram_media_id, effective_object_story_id, image_hash, image_url, instagram_permalink_url, instagram_story_id, instagram_user_id, link_url, object_id, object_story_id, object_story_spec, object_type, object_url, platform_customizations, product_set_id, status, template_url, thumbnail_url, title, url_tags, use_page_actor_override, video_id
date_formatNoFormat for date fields in response. 'U' = Unix timestamp (seconds), 'Y-m-d H:i:s' = MySQL datetime. Default: ISO 8601
limitNoMaximum number of results to return per page (1-100, default: 25)
afterNoCursor for the next page of results, from response.paging.cursors.after
beforeNoCursor for the previous page of results, from response.paging.cursors.before
offsetNoAlternative pagination: number of results to skip
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds behavioral details beyond these: it explains the return structure (object with data and paging), pagination cursors, and date format behavior. No contradictions.

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 well-structured with Args, Returns, and Examples sections, and the core purpose is front-loaded. However, the listing of available fields for the 'fields' parameter is lengthy but necessary. Overall, it's organized and efficient.

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?

For a tool with 7 parameters and no output schema, the description adequately explains the return structure, pagination, and references a sibling tool for pagination. It covers date formats and provides a field list. The absence of output schema is compensated by clear return description.

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. The description adds value by explaining how to use the parameters, including examples for date_format and pagination cursors, and referencing meta_ads_fetch_pagination_url for pagination. This goes beyond simply repeating schema info.

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 action ('Retrieve the ad creatives') and the specific resource ('associated with a specific Meta ad'). It distinguishes from siblings like meta_ads_get_ad_creative_by_id (single creative) and meta_ads_get_adcreatives_by_adaccount (by account) by specifying '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 provides two usage examples ('What creatives are used by ad...' and 'Get the image URLs...') that clarify when to use the tool. However, it does not explicitly state when not to use it or list alternative tools, though the sibling list provides 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/hashcott/meta-ads-mcp-server'

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