Skip to main content
Glama
MrSagarShah

upload-post-mcp

by MrSagarShah

Post a video to social platforms

post_video

Publish a video to multiple social media platforms including TikTok, Instagram, YouTube, LinkedIn, and more. Supports scheduling, first comments, and platform-specific settings.

Instructions

Publish a video to tiktok, instagram (reels/stories), youtube, linkedin, facebook, x, threads, pinterest, bluesky, discord, telegram. The video can be a local file path or a public http(s) URL. 'title' is required for YouTube and Reddit. YouTube extras (tags, categoryId, privacyStatus...), Instagram media_type, TikTok privacy etc. go in extra_params.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesUpload-post profile identifier whose connected social accounts will be used.
titleNoDefault post text / title / caption. Required for YouTube and Reddit; for text posts this IS the post content.
videoYesVideo: local file path or public URL.
timezoneNoIANA timezone for scheduled_date (e.g. 'America/New_York'). Defaults to UTC.
platformsYesTarget platform(s).
subredditNoSubreddit name without 'r/' — required when platforms includes reddit.
thumbnailNoYouTube custom thumbnail: local file path or public URL (max 2MB).
descriptionNoExtended text (LinkedIn commentary, Facebook/YouTube/Pinterest/TikTok descriptions, Reddit body).
add_to_queueNoSchedule into the next available queue slot instead. Cannot combine with scheduled_date.
async_uploadNoReturn immediately with a request_id and process in background (poll with get_upload_status).
extra_paramsNoAny additional platform-specific form fields from the upload-post API docs, passed through verbatim. Examples: {linkedin_title: '...'}, {privacy_level: 'PUBLIC_TO_EVERYONE'}, {media_type: 'REELS'}, {poll_options: ['a','b'], poll_duration: 1440}, {'tags[]': ['tag1','tag2']}.
first_commentNoAutomatically post this as the first comment after publishing.
scheduled_dateNoISO-8601 date/time to schedule publishing (must be in the future, ≤365 days). Omit to publish now.
youtube_privacyNoYouTube privacyStatus.
facebook_page_idNoFacebook Page ID — required when platforms includes facebook (auto-detected if only one page). Use list_page_targets to find it.
pinterest_board_idNoPinterest board ID — required when platforms includes pinterest. Use list_page_targets to find it.
target_linkedin_page_idNoLinkedIn organization page ID to post as a company page instead of the personal profile.
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions scheduling, async upload, and extra_params for platform-specific fields, but lacks details on error handling, rate limits, or the irreversible nature of publishing. Decent but could be more comprehensive.

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 that efficiently packs key information about platforms, video source, and extra_params. It is front-loaded with the main purpose. Slightly dense but without wasted words.

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?

For a tool with 17 parameters, the description covers the main functional points: video source, platform-specific requirements, scheduling, and async mode. It references supporting tools for IDs. Lacks explanation of return values or error handling, but overall fairly complete.

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 100%, but the description adds value by clarifying that title is required for YouTube and Reddit, and by referencing list_page_targets for facebook_page_id and pinterest_board_id. This goes beyond the schema's 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 [list of platforms]', specifies video source options, and notes title requirements for certain platforms. It is distinct from sibling tools like post_photos and post_text.

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

Usage Guidelines4/5

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

The description lists target platforms and mentions that title is required for YouTube and Reddit, providing context. However, it does not explicitly state when to use this tool versus alternatives like post_photos or post_text, though the name implies its use for videos.

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

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