Skip to main content
Glama
Sign In
Reedapt MCP server

Reedapt MCP server

Official
by Reedapt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a dub's files

get_dub_files
Read-only

Retrieve download links for a completed dub, including dubbed video or audio, WAV dubbed audio, and separate voice/background tracks; links expire at expires_at.

Instructions

Download links for a completed dub: the dubbed video or audio, a WAV of the dubbed audio, and the separate voice and background tracks. Links expire at expires_at.

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": {
      "dub_id": "<dub_id>"
    },
    "name": "get_dub_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
dub_idYesThe dub's id, such as dub_…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior — that links are time-limited and expire at `expires_at` — but says nothing about what happens when the dub is not yet complete or how long links last.

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?

Two short sentences, front-loaded with the return content and closed with the expiry caveat. Every clause carries information an agent needs; no filler.

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 compensates by enumerating the returned link types, and it flags link expiry. The only gaps are failure behavior for an incomplete dub and any auth/scope requirements.

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?

Only one parameter, dub_id, with 100% schema description coverage, so the schema already carries the semantics. The description adds no format or sourcing detail about the id beyond what the schema states, which matches the baseline for fully-covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and return type: download links for a completed dub, enumerating the exact artifacts (dubbed video/audio, WAV, voice and background stems). This clearly separates it from metadata-style siblings like get_dub, though no sibling is named explicitly.

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?

The phrase 'for a completed dub' gives a clear precondition: this is only meaningful once a dub has finished, implying wait_for_dub/get_dub polling precedes it. No explicit exclusions or named alternatives, so it stops short of a 5.

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

Deploy Server

Other Tools