Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

mux_act

Destructive

Get a video into Mux. Each call makes a new upload or asset (never retried, no deduplication): Mux bills storage and delivery per video.

op:

  • create_upload — a direct upload address. The answer's data.url takes the video file in ONE HTTP PUT, with no credential (the address is the authorisation), from wherever the file is: e.g. curl -X PUT --upload-file film.mp4 -H "Content-Type: video/mp4" "<url>". The file never passes through this tool. Then mux op='get_ingest' gives the asset_id, and op='get_asset' says when it is ready. The address expires after timeout seconds (60 to 604800, default 3600).

  • create_asset — a video from a file Mux fetches itself at input_url (https, public or pre-signed). The answer's data.id is the asset.

Playback is public unless playback_policy="signed" (a signed playback needs tokens this connector does not make). test=true makes a free 10-second watermarked video, deleted after a day: for trying the flow.

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": {
      "op": "<op>"
    },
    "name": "mux_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesWhat to make (see above).
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
testNoMake a free 10-second test video instead of a real one.
titleNoThe video's title, shown in the Mux dashboard.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
timeoutNo`create_upload` only: seconds before an unused address expires, 60 to 604800.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
input_urlNoThe https address of the file, for `create_asset`.
cors_originNo`create_upload` only: the origin allowed to PUT from a browser, or `*`.
passthroughNoUp to 255 characters of your own, returned on the asset, e.g. to recognise it later.
video_qualityNo`basic`, `plus` or `premium`, billed differently; Mux's default when omitted.
playback_policyNo`public` (default) or `signed`.
max_resolution_tierNoHighest resolution stored and streamed: `1080p`, `1440p` or `2160p`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds real cost and side-effect context: no retries, no deduplication, per-video storage and delivery billing. It further discloses that the upload URL is itself the authorization, that the file never passes through the tool, that addresses expire in 60–604800s, and that signed playback needs tokens this connector cannot mint.

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?

Front-loads the core purpose and cost warning, then splits the two ops into a tight bulleted list with a runnable curl example. Dense but every sentence carries operational information; no 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 15-parameter, no-output-schema mutation tool, the description compensates by naming the return fields an agent needs (`data.url` for uploads, `data.id` for assets) and describing the end-to-end ingest-to-ready flow. Remaining gaps are platform-standard scoping params already documented in the schema.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond it: timeout range and default, the https/public-or-pre-signed nature of input_url, the fact that playback_policy='signed' is unusable here, and that test=true yields a free 10-second watermarked video deleted after a day. The identity/scoping params (_org, _group, _project, _instance, _run_id) are left entirely to the 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?

States a specific verb and resource ('Get a video into Mux') and then enumerates the two concrete operations, create_upload and create_asset, with the mechanics of each. An agent can distinguish this from the read-only `mux` sibling without opening the 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?

Gives explicit selection criteria per op: create_upload when the file is local and you want to PUT it yourself, create_asset when Mux should fetch it from `input_url`. It also routes the agent onward ('mux op=get_ingest gives the asset_id, get_asset says when it is ready') and flags `test=true` for trying the flow.

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

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