Meta Ads by Get MCP Ads

meta list ad images

meta_list_ad_images

Read-onlyIdempotent

List ad account image library entries—hashes, names, dimensions, status, permalink, and CDN URLs—and optionally show 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

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

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.

Changed4 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / minHeight / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / minWidth / maximum
```
Added value: +9007199254740991
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety bar is met; the description adds genuine operational context beyond that by labeling permalink_url as permanent and publicly served while the CDN URLs are short-lived — a behavioral detail an agent needs for caching decisions. It stops short of mentioning pagination limits, permissions, or rate-limit behavior.

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?

A single front-loaded sentence with no filler, leading with the verb, the resource, and the API path. The trailing field enumeration partly duplicates the output schema, which is minor waste but also the most scannable part of the line.

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?

With an output schema present, the description need not enumerate return fields, yet it still surfaces the one return detail an agent must act on (permalink stability vs. expiring CDN URLs). Gaps remain around pagination behavior and whether adAccountId must be the act_-prefixed form for this endpoint, though the schema covers the latter.

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 the schema already documents all eight parameters including hashes, minWidth/minHeight, nameFilter, cursor, and limit. The description only restates includeUsage in prose ("optionally the creatives using each image") and adds no filtering syntax or matching semantics beyond what the schema provides; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the ad account image library (/adimages)") and enumerates the returned fields, so an agent knows exactly what it gets back. It is distinguishable from meta_get_creative_assets and meta_list_ad_videos by resource, but it never names those siblings to confirm the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use or when-not-to-use guidance and never routes the agent between this tool and the many sibling listing tools (meta_get_creative_assets, meta_list_ad_videos, meta_get_creatives). The optional includeUsage flag is the only hint about a usage decision, and its trade-off is not explained.

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

Deploy Server