Meta Ads by Get MCP Ads

meta list ad images

meta_list_ad_images

Read-onlyIdempotent

List ad account images with hash, name, dimensions, status, and display URLs. Optionally include the creatives using each image.

Instructions

List the ad account image library (/adimages): hash, name, dimensions, status, a permanent publicly served display URL (permalink_url), short-lived CDN URLs, and optionally the creatives using each image.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`cursor`	No	Pagination cursor from previous response
`hashes`	No	Only these image hashes (exact match)
`minWidth`	No	Only images at least this wide, in pixels
`minHeight`	No	Only images at least this tall, in pixels
`nameFilter`	No	Only images whose file name matches this value
`adAccountId`	Yes	Ad account ID (e.g., act_123456789)
`includeUsage`	No	Also return the creative IDs using each image

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Sep 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds useful context: returns permanent display URL vs short-lived CDN URLs, and includes optional creative usage. It doesn't contradict annotations. The openWorldHint implies pagination, which is supported by the cursor parameter.

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?

A single sentence with front-loaded resource and a clear list of returned fields, plus the optional includeUsage. No filler or repetition.

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 output schema exists, the return fields are covered. The description mentions pagination implicitly via the cursor and openWorldHint, but could explicitly state that not all images may be returned without pagination. However, the schema covers cursor and limit, so the description is sufficient.

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 parameters are fully described. The description reiterates the main return fields but doesn't add semantic detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb ('list') and resource ('ad account image library /adimages') and explicitly enumerates the fields returned. Clearly distinct from siblings like meta_list_ad_videos and meta_get_creative_assets, with the openWorldHint indicating partial returns.

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 clearly states the tool lists ad images with optional filtering and creative usage. It does not explicitly name alternatives or when not to use it, but the scope is evident. Could mention not to use for videos or other assets, but sibling names make the distinction clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server