Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Upload From Device

open_upload_widget

Opens an upload box so users can add photos, videos, or documents from their phone or computer when files lack a public URL, then returns public media URLs for posting.

Instructions

Let the user add photos, videos or documents from their phone or computer. Use it when the user wants to post a file that has no public URL, such as a photo on their phone, a file attached in the chat that upload_media cannot read (in ChatGPT, pass attached files to upload_media as attachments instead), or a file you built in a sandbox whose network blocks the get_upload_urls uploadUrl. Never suggest putting the files in a public GitHub repo or a file-sharing link instead. In apps that show MCP Apps widgets, such as ChatGPT and Claude chat, it shows an upload box in the chat, and when the upload finishes the box sends a message listing the public media URLs. In apps that cannot show the box, such as Claude Cowork and Claude Code, it returns status upload_link with uploadUrl, a page the user opens in their browser to upload, and uploadId: give the user the link, wait until they say they finished, then call this tool again with that uploadId to get the media URLs. Pass the media URLs as mediaUrls to create_post, update_post or bulk_schedule_posts. Nothing is uploaded until the user picks files. Accepts JPEG, PNG, WebP, GIF, MP4, QuickTime, PDF, PPT, PPTX, DOC and DOCX, up to 250 MB per file, 50 MB per image and 100 MB per document. Uploaded files are stored at public URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_upload_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
uploadIdNouploadId from an earlier call that returned an upload link. Returns the files the user uploaded through that link instead of opening a new upload.
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesWithout uploadId: status waiting_for_upload when the upload box is shown (the media URLs arrive later in a message from the box), or status upload_link with uploadUrl, uploadId and acceptsUntil. With uploadId: status (waiting, saving, ready, failed or expired), files ({ fileName, publicUrl } each), mediaUrls, failed ({ fileName, error } each), savingCount and acceptsUntil.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well past the annotations (readOnlyHint=false, destructiveHint=false, idempotent=false) by disclosing that nothing is uploaded until the user picks files, the app-dependent branching (widget message with URLs vs. an upload_link page), the two-step uploadId resume flow, and that files land at public URLs. It omits retention/privacy of stored media, and the long single paragraph makes the branching easy to skim past, so it stops short of a 5.

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?

Purpose and the main routing decision are front-loaded, and nearly every clause carries information an agent needs. However, the middle section is a run-on with stacked parentheticals that mixes usage rules, environment branching, and format limits, which makes it harder to parse than a short bulleted structure would be.

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?

Covers everything an agent needs for a 2-parameter, non-destructive tool with an output schema: entry conditions, environment-dependent return forms, the resume flow, accepted formats and size limits, and the downstream tools that consume mediaUrls. Return-value details are already handled by the output schema, yet the description still summarizes them usefully.

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?

Schema description coverage is 100%, and the schema already explains uploadId as resuming a prior upload link and workspaceId as the acting workspace. The description restates the uploadId resume flow ('call this tool again with that uploadId') but adds no format, constraint, or edge-case meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('let the user add photos, videos or documents from their phone or computer') and immediately differentiates from siblings by naming the cases where upload_media or get_upload_urls do not work. An agent can identify this as the file-picker/upload-box tool without inspecting schemas.

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?

Explicit when-to-use conditions (no public URL, sandbox file with blocked network, chat attachment upload_media cannot read), an explicit when-to-use-otherwise routing (pass attachments to upload_media in ChatGPT), and an explicit prohibition (never suggest public GitHub repo or file-sharing link). It also states the correct follow-up call to consume the returned URLs.

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