Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get Meta Ad Creative by ID

meta_ads_get_ad_creative_by_id
Read-onlyIdempotent

Fetch detailed fields of a specific Meta ad creative by providing its creative ID. Choose from available fields to get body, title, image URL, call-to-action, and more.

Instructions

Retrieve detailed information about a specific Meta ad creative.

Args:

  • creative_id (string): Ad creative ID, e.g., '23842312323312'

  • 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

  • thumbnail_width (number): Width of the thumbnail image in pixels (default: 64)

  • thumbnail_height (number): Height of the thumbnail image in pixels (default: 64)

Returns: Object with the requested creative fields.

Examples:

  • Use when: "Get the body text, title, and image URL for creative 23842312323312"

  • Use when: "What is the call-to-action type and status of this creative?"

  • Use when: "Get a larger thumbnail (300x200) for this creative"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
creative_idYesAd creative ID, e.g., '23842312323312'
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
thumbnail_widthNoWidth of the thumbnail image in pixels (default: 64)
thumbnail_heightNoHeight of the thumbnail image in pixels (default: 64)

Tool Definition Quality

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, so the description's statement 'Retrieve detailed information' adds minimal behavioral context beyond the structured data. No additional traits like rate limits, auth needs, or return format beyond 'Object'.

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 clear sections for args, returns, and examples. It is front-loaded with the purpose. Each sentence adds value, though it could be slightly shortened while preserving clarity.

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?

Given 4 parameters and no output schema, the description explains the return type as an object with requested fields, which is adequate. It covers the main usage patterns with examples. It lacks details on error handling but is sufficiently complete for a read-only tool with good annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description lists available fields and provides examples, but the schema already describes all parameters. The description does not add new meaning beyond what is in the schema for each param.

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 'Retrieve detailed information about a specific Meta ad creative,' which is a specific verb+resource. It distinguishes from sibling tools like meta_ads_get_adcreatives_by_adaccount (list) and meta_ads_get_ad_creatives_by_ad_id (different) by focusing on a single creative by 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 concrete 'Use when' examples that illustrate typical scenarios (e.g., getting body text, call-to-action, thumbnail). It implies the tool is for retrieving a specific creative by ID but does not explicitly state when not to use it or what alternatives exist.

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