Skip to main content
Glama
Sign In

ShortSync

by app.shortsync
OverviewDiscussionsAdmin

Create upload

create_video_upload

Reserves a NEW video/image library slot and returns a presigned S3 PUT URL for the caller to upload bytes directly. Use this when you have the file locally and don't want to host it publicly first (create_video_upload_from_url is the URL-based alternative). Response: { upload_id, presigned_url, method: 'PUT', expires_at, required_headers? }. PUT the raw bytes to presigned_url with Content-Type set to the file's MIME (video/mp4, video/quicktime, video/webm, image/jpeg, image/png, image/webp, image/gif). S3 records whatever type you send and finalize validates it against the allow-list. If required_headers is present, echo those verbatim on the PUT or S3 will 403 with SignatureDoesNotMatch. After the PUT completes, call finalize_video_upload with upload_id to get the video_upload_id back. Video max 950 MB, image max 20 MB.

DO NOT use this tool to set a cover / thumbnail on an existing video post. This creates a separate library entry, not a cover image. To set a cover on an existing post, call update_post with custom_thumbnail_url (public https URL to an image) or with custom_thumbnail_upload_id (a video_upload_id of an image already in the workspace).

Input Schema

NameRequiredDescriptionDefault
filenameNoOptional original filename (max 255 chars, no path separators). Preserved on the video_uploads row after finalize so the dashboard and platform validators can read the extension. When provided the response includes a required_headers map that the client MUST echo on the PUT.
workspace_idYesWorkspace to attach the upload to. Get one from list_workspaces.
idempotency_keyNoOptional client-generated key (e.g., a UUID) to make retries safe. Identical calls with the same key within 10 minutes return the original result instead of running the write twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it describes the response object, the required PUT method, Content-Type constraints, the 403 risk when required_headers are not echoed, size limits, and the need to call finalize_video_upload afterward. These details go well beyond the safety hints in the annotations and do not contradict them.

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 appropriately long for a multi-step upload workflow and is front-loaded with the core action, the alternative sibling, the response shape, PUT instructions, limits, and the finalize step. Each section serves a clear operational purpose.

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?

Although there is no output schema, the description explicitly documents the response fields including upload_id, presigned_url, method, expires_at, and required_headers. It also gives enough workflow guidance to complete the upload and finalize it correctly, including constraints and the follow-up 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?

Schema description coverage is 100%, so workspace_id, filename, and idempotency_key are already well documented in the schema. The description reinforces the filename/header workflow and upload constraints, but it does not add significant parameter-level meaning beyond what the schema provides.

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 states a specific verb and resource: it reserves a NEW video/image library slot and returns a presigned S3 PUT URL. It clearly distinguishes itself from the sibling create_video_upload_from_url and from thumbnail-setting behavior on existing posts.

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 gives explicit when-to-use guidance: use this when the file is local and you do not want to host it publicly first, with create_video_upload_from_url named as the URL-based alternative. It also gives an explicit DO NOT case for cover/thumbnail creation and routes that use case to update_post with the appropriate parameters.

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

All ShortSync toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources