Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_social_transcript_cleaner

Clean raw social transcripts, VTT, or SRT by removing timestamps, fillers, and duplicate lines for analysis-ready text.

Instructions

[Social Analytics] Clean a raw transcript/VTT/SRT: timestamps, fillers, duplicates Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://social.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
transcriptYesRaw transcript text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole burden. It does add genuine operational context beyond the schema: a hosted endpoint (social.caelaralabs.com) and measured latency (p50 12 ms, p95 14 ms). However, it never states whether the operation is stateless/non-persistent, whether the original is preserved, or what the response contains — gaps that matter for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, which is good. But the benchmark citation with date and domain plus the bare endpoint URL read as marketing rather than decision-relevant content, and the run-on 'duplicates Measured p50 12 ms' is malformed prose.

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

Completeness3/5

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

For a one-parameter text transform, the description covers input formats and performance but omits any indication of the return value (cleaned text only? a report of what was stripped?). With no output schema, that omission leaves a real gap an agent must guess at.

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% and there is a single required parameter, so the schema already does the basic work. The description still adds meaning by specifying accepted formats (raw text, VTT, SRT), which the bare 'Raw transcript text' schema label does not convey.

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?

Uses a specific verb (Clean) with a concrete resource (raw transcript/VTT/SRT) and enumerates the artifacts removed: timestamps, fillers, duplicates. An agent can immediately tell what the tool produces. It stops short of naming any sibling it is distinct from, but no sibling in the list appears to overlap on transcript cleaning.

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 statement of when to use this versus any alternative, nor any prerequisite (input size limits, supported format caveats). The only usage signal is implicit in the phrase 'raw transcript/VTT/SRT', which suggests the input shape but not the decision context.

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