Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

mux

Read-only

Mux Video, read-only: the videos (assets) of the token's environment, and the direct uploads that make them.

op:

  • list_assets — newest first: id, status, duration (seconds), resolution, playback ids, passthrough, title. limit 1-100 (default 25), next_cursor in the answer goes into cursor. With upload_id: the asset that upload made. Tightened by default (tracks, rendition and master-file settings, input diagnostics), the answer's projection naming what was removed: full=true returns the raw records.

  • get_asset — one asset (asset_id). status is preparing until Mux has processed the file (about the film's length), then ready or errored (with errors).

  • get_ingest — one direct upload made by mux_act op='create_upload' (upload_id): status is waiting until the file is PUT, then asset_created with its asset_id (or errored, cancelled, timed_out).

Every PUBLIC playback id carries its stream_url (https://stream.mux.com/<id>.m3u8, HLS), the address a player takes.

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

Input Schema

NameRequiredDescriptionDefault
opYesWhat to read (see above).
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
fullNo`list_assets`: the raw records instead of the tightened view.
limitNoAssets per page, 1 to 100 (`list_assets`).
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
cursorNo`next_cursor` of the previous page (`list_assets`).
_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.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
asset_idNoThe asset, for `get_asset`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
upload_idNoThe direct upload, for `get_ingest`; or, with `list_assets`, the upload whose asset to find.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description stays consistent with that. It adds real behavioral context beyond annotations: results are tightened by default with a named list of removed fields, `projection` records what was stripped, and `full=true` is the escape hatch; it also documents the status lifecycles (`preparing`/`ready`/`errored`, `waiting`/`asset_created`/`timed_out`) and the latency expectation. It says nothing about auth/instance requirements or rate limits, so it is good rather than complete.

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 read-only scope, then a bullet per op, which is the right shape for a three-mode tool. Every line carries information, though a few phrases are compressed to the point of being cryptic ("Tightened by default ... the answer's `projection` naming what was removed") and demand a re-read.

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?

With no output schema, the description correctly carries the return-value burden, enumerating the fields each op yields and the HLS `stream_url` format for public playback ids. What is missing is modest: error shapes for `list_assets` and any note on environment/instance resolution for an 11-parameter tool.

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 the baseline is 3, but the description earns more: it fixes `limit` to 1-100 with default 25, explains that the response's `next_cursor` feeds `cursor`, and calls out the dual role of `upload_id` (the lookup key for `get_ingest`, a filter for `list_assets`). It leaves the context parameters (`_org`, `_run_id`, `_project`, `_instance`) 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?

Names the specific service (Mux Video), the scope (read-only, the token's environment), and the exact resources: assets and the direct uploads that create them. The three `op` values are each described with a distinct verb-resource pair, and the read-only framing cleanly separates it from the sibling `mux_act`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear context for each op and explicitly points at `mux_act` op='create_upload' as the thing that produces the uploads `get_ingest` reads, so the read/write split is inferable. It never states an explicit when-not or a decision rule between `get_asset` and `list_assets` with `upload_id`, which are near-overlapping lookups.

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