WritersLogic verifiable AI agents

transcribe-url

Transcribe an audio or video file URL (Whisper, timestamps, SRT, VTT) — Transcribes a public audio or video FILE URL (podcast enclosure, meeting recording, voice memo; mp3, wav, mp4/m4a, ogg, webm, flac; up to 25 MB and 30 minutes) with Whisper large-v3-turbo on Cloudflare Workers AI. Returns timestamped segments plus SRT and VTT subtitles and the plain text, bound to the media's SHA-256. Does NOT accept YouTube, Spotify or any streaming page (the URL must be the medi

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": {
      "url": "<url>"
    },
    "name": "transcribe-url"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	https URL of the audio or video file itself.
`formats`	No	Outputs to include; default all.
`language`	No	ISO 639-1 language code of the speech (for example en); detected when omitted.
`max_minutes`	No	Reject audio longer than this, default 30.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it names the model (Whisper large-v3-turbo), the provider, the hard limits (25 MB, 30 minutes), the return payload (timestamped segments, SRT, VTT, plain text, bound to the media SHA-256) and the acceptance restriction. It omits failure behavior, cost/auth requirements and rate limits, keeping it short of a 5.

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 content is front-loaded, but the leading parenthetical tagline ('Whisper, timestamps, SRT, VTT') is then restated almost verbatim in the sentence that follows, and the text appears truncated mid-clause. Redundancy costs efficiency without losing meaning.

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 a tool with no annotations and no output schema, the description covers inputs, hard limits, outputs and exclusions adequately. Missing pieces are edge-case behavior (oversized or long media, failures) rather than anything needed to make a correct first call.

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 100%, so all four parameters are already documented, including the ISO 639-1 pattern and defaults. The description adds little parameter-level meaning beyond restating that SRT/VTT/text are produced and that audio is capped at 30 minutes; baseline 3 applies.

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 ('Transcribe an audio or video file URL') and immediately scopes the resource to a file (not a page), listing accepted container formats. The explicit exclusion of YouTube/Spotify/streaming pages makes the boundary of the tool unambiguous.

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?

Gives clear when-to-use context (podcast enclosure, meeting recording, voice memo) and a hard when-not (no YouTube, Spotify or any streaming page; the URL must be the media file itself). It does not route the agent to any alternative tool for streaming URLs, which is the only gap.

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

All WritersLogic verifiable AI agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?