Skip to main content
Glama

meta_ads_creatives_list

List ad creatives from a Meta Ads account to audit inventory or retrieve creative IDs for reuse.

Instructions

Lists AdCreative resources in a Meta Ads account. Returns id, name, status, object_story_id, call_to_action_type, and thumbnail_url per creative. Read-only — does not modify the account. Default limit is 50 creatives per call (max 1000); for larger inventories use smaller limits and filter client-side. Use this to audit creative inventory or to find a creative_id for reuse in meta_ads_ads_create. To list the ads that consume these creatives, use meta_ads_ads_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
limitNoMax creatives returned in a single call. Default 50, maximum 1000 per Meta Graph API.
Behavior4/5

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

Discloses read-only nature and default/max limit. No annotations provided, so the description adds behavioral context beyond the schema. Could mention authentication or rate limits, but sufficient for a simple list tool.

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?

Three concise sentences, each contributing valuable information. Front-loaded with purpose, no fluff.

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?

Covers purpose, usage, and key behavioral traits. Missing mention of pagination details (e.g., cursor), but acceptable for a list tool with limit/max noted. Complete enough given tool simplicity.

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 coverage is 100%, so baseline 3. Description adds minimal extra: clarifies account_id fallback and 'act_' prefix, and limit default/max. Adequate but not exceptional.

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?

Clearly states it lists AdCreative resources, specifies returned fields (id, name, status, etc.), and distinguishes from sibling meta_ads_ads_list for listing ads that consume creatives.

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 states when to use: auditing creative inventory or finding creative_id for meta_ads_ads_create. Provides alternative tool for listing ads and notes limit behavior for large inventories.

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