Meta Ads by Get MCP Ads

meta list ad videos

meta_list_ad_videos

Read-onlyIdempotent

List videos in a Meta ad account video library, with filters for title and duration, pagination, and optional short-lived source file 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

TableJSON 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

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

Behavior4/5

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

Annotations already mark it read-only, open-world, idempotent, and non-destructive. The description adds valuable behavioral context beyond those annotations: publicly served thumbnails, short-lived source URLs that are returned only on request, and the specific API endpoint. No contradictions with annotations.

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?

Two sentences, front-loaded with endpoint, scope, and returned fields, followed by a caveat about source URL expiry. Every clause carries information and there is no fluff.

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?

With an output schema present and annotations covering read-only/idempotent behavior, the description does not need to explain return values. It covers endpoint, fields, and the one behavioral caveat (URL expiry) that affects invocation, making it sufficient for correct use.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the 'includeSource' trade-off (short-lived URLs) and the thumbnail size behavior, which is not present in the parameter schema.

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 uses a specific verb ('List') and resource ('ad account video library (/advideos)') and enumerates the returned fields: title, duration, processing status, and publicly served thumbnails. This clearly distinguishes it from sibling get/list tools without needing to name them.

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

Usage Guidelines3/5

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

No explicit alternatives or when/when-not conditions are provided; usage is implied by 'List the ad account video library.' The only guidance is that source file URLs are returned only on request because they expire quickly, which frames parameter choice rather than tool selection.

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

Deploy Server