Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_videos_upload

Get a video into Meta Ads by providing a public HTTPS URL. Returns a video_id; poll its status until ready, then use it in creative tools.

Instructions

Uploads a video to the Meta Ads account by fetching it from a public HTTPS URL. Returns the video_id to reference in creative-construction tools. Mutating — the asset is persisted. Meta fetches the URL itself and then processes the video asynchronously: poll meta_ads_videos_get until status.video_status reports ready (typically a few minutes) before attaching it to a creative. Supported formats: MP4, MOV, AVI, WMV, MKV, up to 1 GB via this tool; larger files need resumable upload (not yet supported). For uploads from local files use meta_ads_videos_upload_file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional title stored with the uploaded video. Used for library organization; not shown in ads.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
video_urlYesPublic HTTPS URL of the video. Meta fetches it once at upload time. Supported formats: MP4, MOV, AVI, WMV, MKV, up to 1 GB; larger files need resumable upload (not yet supported).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / video_url / description
      Previous value: -"Public HTTPS URL of the video. Meta fetches it once at upload time. Supported formats: MP4, MOV. Recommended max 4 GB."New value: +"Public HTTPS URL of the video. Meta fetches it once at upload time. Supported formats: MP4, MOV, AVI, WMV, MKV, up to 1 GB; larger files need resumable upload (not yet supported)."
  3. Addedv0.9.12
  4. Removedv0.9.6
  5. Addedv0.9.2
  6. Removedv0.9.1
  7. Addedv1.0.5

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Mutating — the asset is persisted,' making the side effect clear. It discloses the asynchronous processing (Meta fetches the URL and processes it asynchronously) and instructs polling. It also lists supported formats and size limits, which are not covered by annotations. This is thorough and transparent.

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 well-structured and concise. It front-loads the core action and return value, then provides essential behavioral details (mutating, async), then format/size constraints, and finally the sibling alternative. Every sentence earns its place with no fluff or redundancy. It is efficiently organized and easy to parse.

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?

For a mutation tool with async behavior and no output schema, the description is exceptionally complete. It explains the full workflow (upload, poll, attach), the constraints (formats, size), the fallback for local files, and the return value. An agent has everything needed to use this tool correctly without guessing.

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?

The schema already has 100% coverage, so the baseline is 3. The description adds meaningful context beyond the schema: it clarifies that the video_url is fetched once by Meta, reiterates the 1 GB limit, and explains the account_id fallback. It also introduces the concept of the returned video_id, which is not in the schema but is essential for downstream creative construction. While some of this is duplicated, the overall added context elevates it slightly above baseline.

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 the tool's purpose: uploading a video from a public HTTPS URL to the Meta Ads account. It specifies the verb (upload), the resource (video), and the return value (video_id). It also explicitly distinguishes itself from the sibling tool meta_ads_videos_upload_file by saying 'For uploads from local files use meta_ads_videos_upload_file,' making it immediately clear which tool to use for which scenario.

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?

The description provides explicit usage guidance: it tells the agent when to use this tool (for public URL uploads) and when to use the alternative (local files). It also gives a crucial after-upload step: 'poll meta_ads_videos_get until status.video_status reports ready... before attaching it to a creative.' It further notes that larger files need resumable upload, which is not yet supported, so the agent knows the limitations upfront.

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

Deploy Server

Other Tools