Meta Ads by Get MCP Ads

meta list ad videos

meta_list_ad_videos

Read-onlyIdempotent

List and filter an ad account's video library, returning titles, durations, processing status, thumbnails, and optional short-lived source URLs.

Instructions

List the ad account video library (/advideos): title, duration, processing status, and publicly served thumbnails (preferred and largest sizes). Source file URLs are returned only on request because they expire quickly.

Input Schema

Name	Required	Description
`limit`	No	Videos per page (thumbnail payloads are heavy, keep this modest)
`cursor`	No	Pagination cursor from previous response
`adAccountId`	Yes	Ad account ID (e.g., act_123456789)
`titleFilter`	No	Only videos whose title contains this value
`includeSource`	No	Also return the short-lived raw video file URL for each video
`maxLengthSeconds`	No	Only videos at most this many seconds long
`minLengthSeconds`	No	Only videos at least this many seconds long

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.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

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.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds useful context beyond the annotations: thumbnails are publicly served in preferred and largest sizes, and source file URLs are returned only on request because they expire quickly.

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?

The description is two compact sentences with no wasted language. The core identity is front-loaded, and the thumbnail and source-URL details are appropriately secondary.

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 rich annotations, 100% schema coverage, and an output schema, the description covers the essential behavior an agent needs to call the tool correctly. It could still be slightly more complete by mentioning pagination or when to prefer sibling video-source tools, but it is adequate for this list operation.

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 description coverage is 100%, so the schema already documents all seven parameters, including limit, cursor, filters, and includeSource. The description adds behavioral meaning for includeSource by explaining why source URLs are opt-in, but it does not deepen semantics for the remaining parameters beyond what the schema provides.

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?

The description clearly states a specific verb and resource: listing the ad account video library (/advideos), and it enumerates the returned fields. It is distinguishable from image-list siblings by its explicit video focus, but it does not directly name or contrast with likely alternatives such as meta_get_video_sources or meta_get_uploaded_video.

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 implies usage by describing what the tool lists, but it gives no explicit when-to-use guidance, no exclusions, and no alternatives. It does not tell the agent when to choose this tool over sibling tools such as meta_get_video_sources or meta_list_ad_images.

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

Deploy Server