Skip to main content
Glama

TranscriptLab

Submit a batch transcript job

transcriptlab_submit_batch

Queue a list of YouTube URLs as one batch job and return its job id. App-facing only. The plan caps how many URLs one job accepts.

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": {
      "urls": "<urls>"
    },
    "name": "transcriptlab_submit_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesYouTube URLs to transcribe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the call is asynchronous (returns a job id, not transcripts) and a plan-level quota caps URLs per job, which the agent needs before batching.

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?

Three short sentences with the core action front-loaded, then the audience constraint, then the quota caveat. Nothing is padded, though 'App-facing only' is terse to the point of ambiguity.

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 mutation-style async submit tool with no output schema, the description states the return (job id) adequately. It omits the obvious next step (polling transcriptlab_get_job_status / listing items) and says nothing about what happens on partial failure or over-cap submissions.

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% with a single well-described 'urls' array (minItems 1, maxItems 500), so the baseline is 3. The 'plan caps how many URLs one job accepts' sentence adds a real constraint beyond the schema's static maxItems, but it gives no numbers or per-plan detail.

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 names a specific verb and resource: queue a list of YouTube URLs as one batch job and return the job id. That is clearly distinguishable from the single-transcript siblings, though it never names an alternative explicitly and 'App-facing only' is a scope note rather than a differentiation.

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?

'App-facing only' is a constraint, not usage guidance. There is no statement of when to choose this batch tool over single-URL options like transcriptlab_transcribe_media_url, nor any exclusion of non-YouTube sources, so the agent must infer the boundary from the tool name and sibling list.

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.