Skip to main content
Glama

Rigged Clean

enhance_media

Clean speech in a video or audio file. Submit a public HTTPS URL or a completed upload, wait briefly, then poll get_job if running. Keyless requests preview the first minute. Paid jobs may spend credits.

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

Input Schema

NameRequiredDescriptionDefault
tierNo
previewNo
loudnessNo
strengthNo
upload_idNoAn upload ID whose PUT has completed. Supply exactly one source.
source_urlNoPublic HTTPS URL. Supply exactly one source.
audio_trackNo
max_cost_usdNoMaximum charge in US dollars.
wait_secondsNoSeconds to wait for a terminal state. Default 45 for submission, 0 for polling.
idempotency_keyNoReuse for retries of the same submission.
anonymous_sessionNoKeyless session credential. Save the value returned on your first call and pass it on related calls and retries.

Output Schema

NameRequiredDescriptionDefault
idYes
tierYes
errorNo
stageNo
engineNo
job_idYes
resultNo
statusYes
billingNo
previewYes
receiptNo
download_curlNo
anonymous_sessionNoKeyless session credential. Save the value returned on your first call and pass it on related calls and retries.
processed_secondsNo
poll_after_secondsNo
full_file_price_usdNo
full_file_price_micro_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation. The description adds valuable behavioral context: asynchronous job handling, polling with get_job, first-minute preview limits, and potential credit charges.

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?

The definition is three tight sentences with the core action and workflow front-loaded. Every sentence carries useful selection or invocation information, with no repetition or 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?

For an 11-parameter asynchronous job submission tool, the description covers the essential lifecycle, source options, preview behavior, and cost warning, while the output schema handles return values. The main remaining gaps are explanations of the optional processing controls.

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 only 55%, and the description clarifies source selection, waiting, preview, and cost behavior. However, it adds little or no meaning for optional controls such as tier, loudness, strength, audio_track, and idempotency_key.

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: clean speech in a video or audio file. It also names the two accepted source types and routes polling to get_job, which clearly distinguishes it from create_upload and get_job.

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?

Explains the core workflow: submit a public HTTPS URL or completed upload, wait briefly, then poll get_job if still running. It also flags keyless previews and credit spending, though it does not explicitly state when not to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources