Skip to main content
Glama

meta_ads_videos_upload_file

Upload a local video file to your Meta Ads account library and receive a video_id for use in ad creative. Supports MP4 and MOV files up to 4 GB.

Instructions

Uploads a video from a local file path to the Meta Ads account library. Returns the video_id to reference in creative-construction tools. Mutating. Meta processes the video asynchronously after upload — allow a few minutes before attaching the video to ads. For uploads from public URLs use meta_ads_videos_upload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
file_pathYesPath to the video file on the agent's filesystem. Supported formats: MP4, MOV. Recommended max 4 GB.
titleNoOptional title stored with the uploaded video. Used for library organization; not shown in ads.
Behavior4/5

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

Discloses mutating nature and async processing, which are critical behaviors beyond annotations that are absent. Adds value but could mention post-upload status.

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?

Three concise sentences, each providing key information without redundancy. Efficient and front-loaded.

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?

Covers essential behavioral context (async, mutation) and return value. Lacks details on error handling but sufficient for a simple upload tool.

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 baseline 3. The description adds minimal parameter info beyond schema, noting optionality of account_id but not enhancing understanding.

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?

Clearly states 'Uploads a video from a local file path' differentiating it from the sibling tool meta_ads_videos_upload which uses URLs. Specific verb and resource.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool vs. the alternative: 'For uploads from public URLs use meta_ads_videos_upload.' Provides clear guidance.

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/logly/mureo'

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