Skip to main content
Glama
MrSagarShah

upload-post-mcp

by MrSagarShah

Post photos to social platforms

post_photos

Publish single photos or carousels to Instagram, TikTok, LinkedIn, Facebook, X, Threads, Pinterest, Bluesky, Discord, Telegram using local files or public URLs.

Instructions

Publish photo(s) — including carousels — to instagram, tiktok, linkedin, facebook, x, threads, pinterest, bluesky, discord, telegram. Each photo can be a local file path or a public http(s) URL.

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.
photosYesPhoto(s): local file paths or public URLs. Multiple items become a carousel where supported.
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.
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.
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.
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions publishing and platform support but does not disclose potential side effects, rate limits, authentication requirements, or error behavior. This is insufficient for a complex mutation tool.

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 only two sentences, front-loads the core purpose, and contains no unnecessary words. It earns its place without verbosity.

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?

Given 15 parameters and no output schema, the description is adequate but lacks details on platform-specific behaviors, error handling, or prerequisites. Schema descriptions compensate somewhat, but the free-text could be richer for such a complex 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?

The input schema has 100% description coverage, so the description adds minimal value. It mentions that photos can be local files or URLs, which is already in the schema. The carousel mention is a slight addition, but overall the description does not significantly enhance parameter 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?

The description clearly states the verb (Publish) and the resource (photo(s) to multiple social platforms), and specifies the supported platforms. This distinguishes it from sibling tools like post_text and post_video.

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?

The description does not explicitly state when to use this tool versus alternatives like post_video or post_text. It implies usage for images but lacks exclusion criteria or guidance on choosing between similar tools.

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