Skip to main content
Glama

Create media upload link

create_upload_link

Create a single-use Flomixy link (valid about 10 minutes) where the user uploads one image or video from their device. Give the link to the user and tell them it expires at expiresAt. After they upload, call list_media to get the new file url and pass it in mediaUrls. Clients with shell access can skip the user: POST the file as multipart field file to uploadEndpoint (the curl example; answers {id,url,mediaType}), no base64 and no 10 MB inline limit. The link is single-use: one link per file, so 8 slides need 8 calls. Needs the MEDIA_WRITE scope.

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": "create_upload_link"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

There are no annotations, so the description carries the full behavioral burden and does so: single-use semantics, ~10-minute expiry surfaced as expiresAt, one-link-per-file cardinality (8 slides = 8 calls), the required MEDIA_WRITE scope, and the response shape of the direct POST path ({id,url,mediaType}) with no base64 or 10 MB inline cap. These are exactly the constraints that would otherwise cause a failed or mis-sequenced call.

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 validity window are front-loaded, then the user flow, then the shell-client alternative, then cardinality and scope. Every sentence carries operational content, though the single paragraph packs three distinct threads (user handoff, curl path, limits) that would read faster as short separated blocks.

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?

With zero parameters, no output schema, and no annotations, the description supplies everything an agent needs: the entry point, the expiry field to relay, the post-upload retrieval step, the alternate direct-POST route with its return shape, the single-use cardinality, and the required scope. Nothing material is left to inference.

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?

The tool takes no input parameters, so there is nothing schema-side to clarify and the baseline is 4. The description still names the downstream fields the agent must supply (mediaUrls) and the multipart field name `file` for the alternate path, which is useful orientation even though it isn't part of this schema.

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 opens with a specific verb and resource: create a single-use Flomixy upload link with a ~10-minute validity for one image or video from the user's device. That scope statement implicitly separates it from sibling upload_media, which handles inline base64 uploads subject to a 10 MB limit.

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 states when to use this tool (the user uploads from their own device), what to do with the result (hand the link over, tell them the expiry), and the exact follow-up (call list_media and pass the url in mediaUrls). It also names an alternative path for shell-access clients that POST directly to uploadEndpoint, so the agent knows when this tool isn't needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources