Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott

Get Meta Ad Creatives by Ad Account

meta_ads_get_adcreatives_by_adaccount
Read-onlyIdempotent

Retrieve all ad creatives for a Meta ad account with optional filters. Use to audit creative assets or find creatives by condition.

Instructions

Retrieve all ad creatives belonging to a specific Meta ad account.

Useful for auditing all creative assets, finding creatives by status, or reviewing creative content across the account.

Args:

  • act_id (string): Ad account ID prefixed with 'act_', e.g., 'act_1234567890'

  • 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

  • effective_status (string[]): Filter by status: ACTIVE, DELETED, IN_PROCESS, WITH_ISSUES

  • filtering (object[]): Additional filter objects with field, operator, value

  • limit (number): Results per page (1-100, default: 25)

  • after / before (string): Pagination cursors

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

Examples:

  • Use when: "List all active creatives in my ad account"

  • Use when: "Show all creatives with issues in act_123456"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
act_idYesAd account ID prefixed with 'act_', e.g., 'act_1234567890'
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
effective_statusNoFilter by creative status: ACTIVE, DELETED, IN_PROCESS, WITH_ISSUES
filteringNoList of filter objects. Each has 'field', 'operator', and 'value'. Example: [{field: 'spend', operator: 'GREATER_THAN', value: 50}]
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=true, destructiveHint=false, idempotentHint=true. The description adds value by disclosing the pagination mechanism (after/before cursors), the use of meta_ads_fetch_pagination_url for next pages, and the return format (Object with data and paging). 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 clear sections: general description, use contexts, Args with bullet points, Returns, and Examples. It is moderately sized but front-loads the purpose. Could be slightly more concise by not repeating the full field list already present in the schema.

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 the tool's complexity (8 parameters, no output schema), the description adequately covers the main retrieval purpose, filtering options, pagination details, and return structure (data array + paging). It references a sibling tool for pagination, providing sufficient context for an agent to use the tool correctly.

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%, providing a baseline of 3. The description adds meaning beyond the schema by grouping parameters (e.g., 'Fields to retrieve' list, 'Filter by status', 'Additional filter objects') and providing context like the example usage for filtering. It also gives a practical hint for pagination cursors.

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 explicitly states 'Retrieve all ad creatives belonging to a specific Meta ad account', clearly identifying the verb (retrieve), resource (ad creatives), and scope (by ad account). This distinguishes it from siblings like meta_ads_get_ad_creative_by_id and meta_ads_get_ad_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 includes explicit contexts such as 'auditing all creative assets, finding creatives by status, or reviewing creative content across the account' and provides example queries. However, it does not explicitly state when to avoid this tool in favor of alternatives like meta_ads_get_ad_creative_by_id for single creative retrieval.

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