Skip to main content
Glama

Caelara Labs Social Analytics

transcript_cleaner

Clean a raw transcript/VTT/SRT: timestamps, fillers, duplicates

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": {
      "transcript": "<transcript>"
    },
    "name": "transcript_cleaner"
  }
}

Input Schema

NameRequiredDescriptionDefault
transcriptYesRaw transcript text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly drops it. It does not say whether the output is plain text or a cleaned subtitle file, whether timestamps are deleted or repaired, how aggressive filler removal is, whether the original is preserved, or any input size limit. For a transformation tool with zero annotation coverage, this is a substantial 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?

One compact, front-loaded fragment with no wasted words; the verb and the payload come first. The colon-list style is terse to the point of choppiness and leaves terms undefined, but nothing is padded or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required string, no output schema, no nesting), but the description never states the return shape or what survives cleaning, which matters because cleaning can mean strip or repair. Relative to how cheap it would be to say "returns plain text with timestamps removed," the definition is under-specified.

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 coverage is 100% and there is a single well-labeled parameter, so the baseline is 3. The description does add one useful detail beyond the schema — that the input may be VTT or SRT, not just a raw text transcript — which resolves a real question about the `transcript` string's expected format.

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?

The description gives a specific verb ("Clean") and resource ("raw transcript/VTT/SRT") plus the three things removed (timestamps, fillers, duplicates), so an agent can tell what the tool does. Sibling tools are all unrelated analysis/extraction utilities, so no explicit differentiation is required here. It falls short of 5 because "timestamps" is ambiguous — stripped or normalized?

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites, and no alternatives named. The accepted input formats (VTT/SRT/raw text) are implied but never framed as selection guidance. An agent must infer the trigger condition entirely from the tool name.

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