Skip to main content
Glama

studio_link

Read-onlyIdempotent

Open a Cuecaps Studio URL with preset caption settings so users can upload a video, correct words, and export in the browser when manual editing is needed or no Creator/Pro key is available.

Instructions

Returns a URL to the Cuecaps studio, opened with these caption settings, for the user to finish in their browser: they drop in the video, can fix words and export there. Creates nothing and needs no key, so it works on every plan, Free included. Use it when the user wants to edit by hand, has no Creator or Pro key, or the file isn't on this machine; use caption_video to make the file directly.

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

Input Schema

NameRequiredDescriptionDefault
langNoThe spoken language. Give it for any video that isn't in English; auto lets cloud transcription detect it.
linesNoLines per caption.
styleNoCaption style. list_styles shows how each one looks.
wordsNoWords per caption; 1 shows one word at a time.
aspectNoFrame shape: 9:16 for TikTok, Shorts and Reels, 1:1 or 4:5 for feed posts, 16:9 for YouTube.
positionNoWhere the captions sit in the frame.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds context the annotations cannot: it creates nothing server-side, needs no API key, and therefore works on Free plans. It also explains the handoff — the user drops in the video, fixes words, exports in the browser. It stops short of saying whether the URL is stateless or expires, which is the one real gap.

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-loads the return value, then the no-key/no-plan-requirement guarantee, then the when-to-use and the alternative. Every sentence does work, though the single dense paragraph runs slightly long and could be split for scannability.

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?

Six optional parameters, no output schema, no annotations covering semantics — yet the description states what is returned (a URL), that nothing is persisted, that no credentials are needed, and what the user does next. That is everything an agent needs to call it correctly and set expectations.

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 description coverage is 100% with enums and per-parameter descriptions plus hints like 'list_styles shows how each one looks', so the schema carries the semantics. The description only gestures at them collectively as 'these caption settings' and adds no format or default guidance beyond that. Baseline 3 is correct.

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 — returns a URL to the Cuecaps studio pre-loaded with these caption settings — and immediately contrasts it with caption_video, which makes the file directly. An agent can distinguish it from every sibling without opening a 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 rules: use when the user wants to edit by hand, has no Creator/Pro key, or the file isn't on this machine; use caption_video instead to produce the file. Both positive selection criteria and the named alternative are given, leaving nothing to inference.

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