AdaptlyPost

Official

Overview Schema Source Related Servers Discussions Admin

Upload Media

upload_media

Upload images or videos to AdaptlyPost and get public URLs for create_post, update_post, or bulk_schedule_posts. Accepts web URLs or base64 files and returns mediaUrls for direct use in posts.

Instructions

Upload images or videos to AdaptlyPost storage and return public URLs for the mediaUrls of create_post, update_post, or bulk_schedule_posts. Two sources, combinable in one call: urls (public URLs the server downloads and re-hosts) and files (base64 data, for media attached in the conversation). Omitting both returns an error. Accepts image/jpeg, image/png, image/webp, video/mp4, video/quicktime. Stored files are public immediately, post or no post. Prefer this over get_upload_urls, which only mints URLs and leaves the PUT to you. Returns uploaded ({ publicUrl, key } per file) and mediaUrls; pass mediaUrls straight into the post.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	No	Public URLs of images or videos to upload (e.g. ["https://example.com/photo.jpg"])
`files`	No	Direct file uploads as base64. Use this when the user attaches/pastes an image or video in the conversation

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	An object with uploaded (array of { publicUrl, key } per file) and mediaUrls (the public URLs ready to pass to create_post).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The description discloses that files are stored publicly and immediately, that URLs are downloaded and re-hosted, and that base64 files are uploaded. It goes beyond the minimal annotations by explaining the server-side behavior and output shape, though it does not mention rate limits or authentication.

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 dense and informative, but it is a single long paragraph with some repetition (e.g., 'post or no post'). It could be slightly more structured, but the key information is front-loaded and no unnecessary filler is present.

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 the two parameters and nested file object, the description is complete: it covers both input modes, supported MIME types, the required fields for files, the error case, and the return format. It ties the output directly to the expected mediaUrls field used by sibling post-creation tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds important behavioral context: urls are downloaded and re-hosted, files are for attached media, the two sources can be combined, and omitting both is an error. This goes well beyond the raw property names and enum values.

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 uploads images or videos to storage and returns public URLs for use in post creation tools. It explicitly differentiates itself from get_upload_urls by explaining the server re-hosts content rather than just minting URLs.

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?

It names the exact downstream tools (create_post, update_post, bulk_schedule_posts) and explains when to use each parameter source. It also provides an explicit alternative (get_upload_urls) and states the error condition when both sources are omitted.

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

Deploy Server