Skip to main content
Glama
Sign In

oriiion

by ai.oriiion
OverviewDiscussionsAdmin

Create Upload Link

create_upload_link

Get the user's own files (photos, video, PDFs, documents) into their oriiion account when you only have them inside this conversation. Returns a short-lived link the user opens in a browser and drops files on; then call list_uploaded_files for the stored URLs, which work with create_post_from_image, create_carousel_from_images, create_post_from_video and create_document_post. IF YOU HOLD THE FILE AND CAN MAKE HTTP REQUESTS, skip this — it needs nothing from the user: call create_media_upload_url, PUT the bytes, then finalize_media_upload (up to 200MB, no API key needed). If the file is already online, call import_media_from_url. Use this link tool when you cannot make HTTP requests or the file only exists as an attachment in the chat.

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
noteNoOptional short note about what the user should upload — shown to you, not to them

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?

Annotations only give generic hints (non-read-only, non-destructive, non-idempotent), while the description adds meaningful behavior: the link is short-lived, the user must open it in a browser to drop files, and the resulting URLs become available through list_uploaded_files. It also documents the alternative 200MB direct-upload path and that no API key is needed for it.

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 purpose and downstream usage are front-loaded, followed by concise routing guidance for alternatives. Despite covering several paths, every sentence carries decision-relevant information and none is filler.

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?

For a routing tool with a trivial schema and no output schema, the description supplies everything needed: when to call it, what it returns conceptually, how to retrieve uploaded files, and which sibling tools to use instead. Nothing essential is missing.

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?

There is only one optional parameter, note, and schema description coverage is 100%, so the schema already explains that it is a short note not shown to the user. The tool description does not add further meaning beyond the schema, making the baseline 3 appropriate.

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 action and resource: getting the user's own files into their account via a short-lived browser upload link. It clearly distinguishes this from sibling upload paths such as create_media_upload_url, finalize_media_upload, and import_media_from_url.

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 and when-not-to-use guidance: use this when you cannot make HTTP requests or the file only exists as a chat attachment; skip it if you can PUT bytes or the file is already online. It also names the follow-up tool list_uploaded_files and downstream creation tools.

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

All oriiion 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