Skip to main content
Glama

List Ad Videos

meta_list_ad_videos
Read-only

Retrieve a list of videos from an ad account's video library, with options to limit results or paginate using a cursor.

Instructions

Lists videos in an ad account's video library.

Args:

  • ad_account_id (string): Ad account ID

  • limit (number): Max results (default 20)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_account_idYes
limitNo
afterNo
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior3/5

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

Annotations already indicate readOnlyHint=true, so the description doesn't need to restate safety. However, it fails to mention pagination behavior (e.g., use of 'after' for cursors) or response structure.

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 short and front-loaded with the action. However, it omits some detail but still maintains a compact structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 4 parameters and no output schema, the description does not explain pagination, the 'after' cursor, or how results are returned. It lacks completeness for a listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description covers only ad_account_id and limit (2 of 4 parameters) with minimal explanations. The 'after' and 'response_format' parameters are omitted entirely. Schema description coverage is low (25%), yet the description does not compensate.

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 lists videos in an ad account's video library with a specific verb and resource. It distinguishes itself from sibling tools like meta_list_ad_creatives or meta_list_ad_images by focusing on the video library.

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?

No guidance on when to use this tool versus alternatives (e.g., listing ad creatives or images). No mention of prerequisites or context where this tool is appropriate.

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/oliverames/meta-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server