Montik

Create upload

create_upload

A link to send one file from your own machine to the project's media library, good for 60 minutes and one upload. Run the curl command it returns, up to 100 MB a file; the reply is the new media item. For a file with a public URL, use import_media. Counts against the plan's uploads like any file. For a font, use create_font_upload. to: folder sends it to the folder's media, for every project in the folder (add_folder_media adds it here).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`to`	No	folder: the folder's media, shared by its projects (default: this project)
`name`	Yes	File name with its extension, such as voiceover.mp3
`binId`	No	bin to put it in (default: library root)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / to

Added value: +{
+  "description": "folder: the folder's media, shared by its projects (default: this project)",
+  "enum": [
+    "project",
+    "folder"
+  ],
+  "type": "string"
+}

First observedNov 8, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only give the generic non-read-only, non-destructive profile; the description adds the real behavioral facts — the link expires in 60 minutes, works once, caps at 100 MB, must be used via the returned curl command, counts against the plan's upload quota, and the reply is the resulting media item. These are consequences an agent cannot infer from annotations or schema.

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?

Front-loaded with the core purpose and constraints, then sibling routing, with no filler. The trailing sentence about `to: folder` is grammatically rough and partly repeats the schema's enum description, costing it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by explaining the two-part return (curl command to run, then the new media item). With 100% schema coverage and annotations present, the only minor gap is the absence of detail about the returned link/command format.

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 coverage is 100%, including the `to` enum documentation, so the baseline is 3. The description adds only marginal meaning beyond the schema — that `to: folder` places the file in media shared by every project in the folder and that add_folder_media is the alternative path — while `binId` and `name` receive no extra explanation.

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 concrete verb and resource — generate a one-time upload link for a single file into the project's media library — and immediately distinguishes it from import_media (public URL) and create_font_upload (fonts). An agent can select it without opening any schema.

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 routing conditions: use this for a file on your own machine, use import_media for a public URL, use create_font_upload for fonts, and add_folder_media for the folder-scoped variant. It also states the operational window (60 minutes, one upload, 100 MB max) that governs when the call is still valid.

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

All Montik tools Inspect

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

Need Help?