meta-ads-mcp

upload_video

Upload an ad video from a public URL or local file and get a video ID for use in Meta ad creatives.

Instructions

Upload an ad video from a public URL or a local file. Returns video ID for use in ad creatives.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upload_video"
  }
}

Input Schema

Name	Required	Description
`title`	No	Video title
`file_url`	No	Public URL of the video to upload
`file_path`	No	Local filesystem path of the video to upload. Sent as multipart/form-data, bypassing the need for a publicly reachable URL.
`account_id`	No	Ad account ID to upload into (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.
`description`	No	Video description

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.6.1Oct 21, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Ad account ID to upload into (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}

addedInput schema / properties / file_path

Added value: +{
+  "description": "Local filesystem path of the video to upload. Sent as multipart/form-data, bypassing the need for a publicly reachable URL.",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "file_url"
-]
```

First observedv1.2.0Mar 19, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only states the return value and omits permissions needed, rate limits, supported file sizes/formats, asynchronous behavior, and any side effects of the upload.

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 that are front-loaded with the action and outcome, with zero wasted words. It is appropriately sized for the core purpose.

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

Completeness3/5

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

For a five-parameter upload tool with no annotations and no output schema, the description covers purpose and the returned video ID. It leaves out behavioral details such as auth fallback, file constraints, and async behavior that an agent would need for robust invocation.

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 baseline is 3. The description mentions URL and local file sources, which map to file_url and file_path, but adds no syntax, constraints, or fallback details beyond what the schema already documents.

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 ('Upload an ad video') along with source types and the return value. It does not explicitly name or contrast with siblings like upload_image or list_videos, so it misses the top mark for sibling differentiation.

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?

Implies usage by stating 'for use in ad creatives' and offering a choice between public URL and local file. However, it gives no explicit when-to-use, when-not, or alternative-tool guidance, leaving the agent to infer the workflow.

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

Deploy Server