Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott

Get Meta Ad Images

meta_ads_get_ad_images
Read-onlyIdempotent

Retrieve ad images from a Meta ad account to audit assets, filter by hash, name, or dimensions, and check image status.

Instructions

Retrieve ad images belonging to a Meta ad account.

Useful for auditing image assets, finding images by hash or name, and checking image dimensions and status.

Args:

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

  • fields (string[]): Fields to retrieve. Available: id, account_id, created_time, creatives, hash, height, is_associated_creatives_in_adgroups, name, original_height, original_width, permalink_url, status, updated_time, url, url_128, width

  • hashes (string[]): Filter by specific image hashes

  • name (string): Filter images by name (partial match)

  • minwidth (number): Minimum image width in pixels

  • minheight (number): Minimum image height in pixels

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

  • after / before (string): Pagination cursors

Returns: Object with data (image array) and paging. Each image contains URL, dimensions, hash, and status. Use meta_ads_fetch_pagination_url with paging.next for more results.

Examples:

  • Use when: "List all images in my ad account"

  • Use when: "Find images with hashes abc123 and def456"

  • Use when: "Show images wider than 1000px"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
act_idYesAd account ID prefixed with 'act_', e.g., 'act_1234567890'
fieldsNoFields to retrieve. Available: id, account_id, created_time, creatives, hash, height, is_associated_creatives_in_adgroups, name, original_height, original_width, permalink_url, status, updated_time, url, url_128, width
hashesNoFilter by specific image hashes, e.g., ['abc123', 'def456']
nameNoFilter images by name (partial match)
minwidthNoMinimum image width in pixels
minheightNoMinimum image height in pixels
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 and idempotentHint, so the description adds operational context like pagination, return structure, and filtering behavior. No contradiction.

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 sections for purpose, Args, Returns, and Examples. It is comprehensive but not overly verbose; each component serves a purpose.

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?

Given the 10 parameters and no output schema, the description covers return structure, pagination, and usage examples. It also references a sibling tool for pagination, making it self-contained.

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%, but the description adds value by clarifying usage (e.g., 'partial match' for name, example for hashes) and providing a structured Args list with practical details.

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 it retrieves ad images for a Meta ad account, with specific use cases like auditing and filtering by hash/name. It distinguishes from sibling tools like meta_ads_get_image_by_hash by being the general listing tool.

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 explicit examples of when to use, such as 'List all images' or 'Find images with hashes', and notes its utility for auditing. It does not explicitly mention when not to use or alternatives, but the context is clear given sibling tools.

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