Skip to main content
Glama
Upload-Post

Upload-Post

Official

Upload video

upload_video

Publish a video to multiple social media platforms with scheduling, per-platform settings, and AI-generated captions.

Instructions

Publish a video to one or more platforms. Use videoPathOrUrl only for public/signed HTTPS URLs, or for absolute local paths when the MCP server runs on the same machine as the file. Hosted clients such as ChatGPT and claude.ai cannot publish attached files by passing /mnt/data, sandbox, or mounted local paths; for those files, ALWAYS call open_upload_studio first so the browser stages the video to Upload-Post/R2, then publishes it. videoBase64 is only for clients that can provide raw bytes directly and is capped by UPLOAD_POST_MAX_INLINE_MB (default 100). Returns a request_id you can poll with get_status. Supports per-platform overrides (tiktokPrivacyLevel, youtubePrivacyStatus, youtubePlaylistId, youtubeThumbnailUrl, youtubeTags, facebookPageId, instagramMediaType, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesProfile name (Upload-Post user).
titleNoCaption / title.
timezoneNoIANA timezone for scheduled date, e.g. 'Europe/Madrid'.
platformsYesRequired array of platform identifiers, e.g. ['instagram']. Never pass a single string.
addToQueueNoInsert into the user's posting queue instead of publishing now.
asyncUploadNoReturn immediately with request_id (default true).
descriptionNo
videoBase64NoVideo bytes as base64 (or a data: URI). Provide this OR videoPathOrUrl. The server writes it to a temp file, uploads, then deletes it. Capped by UPLOAD_POST_MAX_INLINE_MB (default 100).
autogenerateNoIf true, AI generates native per-platform title/description from the media and fills any field left empty.
firstCommentNo
scheduledDateNoISO 8601 date for scheduled publishing, e.g. '2026-12-25T10:00:00Z'. Omit for immediate post.
videoFilenameNoOptional filename (e.g. 'clip.mp4') used only to pick the temp file extension when videoBase64 is given. Defaults to .mp4.
videoPathOrUrlNoPublic/signed HTTPS URL of the video. Absolute local paths are supported only for local/self-hosted MCP clients sharing the same filesystem. Do not pass ChatGPT `/mnt/data` or sandbox paths; use open_upload_studio instead.
maxPostsPerSlotNo
platformOptionsNoPlatform-specific overrides as a flat object (camelCase keys), e.g. { tiktokPrivacyLevel: 'PUBLIC_TO_EVERYONE', youtubePrivacyStatus: 'public', youtubePlaylistId: 'PLxxxxxxxxxxxx', facebookPageId: '123' }. `youtubePlaylistId` may also be an array or a comma-separated list of playlist IDs to add the uploaded video to.
autogenerateTitleNoGenerate only the title with AI.
autogenerateLanguageNoForce the AI output language (ISO code); omit to auto-detect from the media.
autogenerateDescriptionNoGenerate only the description with AI.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo
Behavior4/5

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

Annotations indicate readOnlyHint=false (mutation) and destructiveHint=false. The description adds context: videoBase64 is capped, asyncUpload returns immediately with request_id, and the server writes to temp file and deletes it. This adds value beyond annotations. No contradictions.

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 a single paragraph but is front-loaded with the core purpose and then provides necessary details. It could be slightly more structured (e.g., bullet points) but is not overly verbose.

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?

Given 18 parameters, 2 required, and an output schema (returns request_id), the description covers main usage, alternatives, file handling, async behavior, and per-platform overrides. It is complete for the tool's complexity.

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 coverage is 83%, so most parameters are described. The description adds high-level context on parameter choice (videoPathOrUrl vs videoBase64) and lists platform-specific overrides. This enriches understanding beyond individual parameter descriptions.

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 'Publish a video to one or more platforms' with a specific verb (publish) and resource (video). It distinguishes itself from siblings like upload_photos, upload_text, upload_document, and specifically references open_upload_studio for an alternative use case.

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 guidance on when to use videoPathOrUrl (public URLs or local paths) vs videoBase64 (raw bytes, capped), and crucially warns against using hosted client paths like /mnt/data, directing to use open_upload_studio instead. This gives clear when-to-use and alternative.

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/Upload-Post/upload-post-mcp'

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