Slice

Transcribe audio or video

transcribe_audio

Use this when the user wants the words: speech in an audio or video file turned into text, from a podcast, interview, lecture, meeting or voice note. Accepts a file the user attached (file) or a direct https link to a media file such as .mp3, .m4a, .wav or .mp4 (url). Returns the transcript with speaker turns, plus a page with the full text and .txt, .srt and .vtt downloads. Short files finish in this call; longer ones return status "processing" and a transcription_id for transcription_status. Up to 90 minutes per file. The first transcript needs no account; after that it asks for a Slice sign-in, and a signed-in person gets 3 transcripts a month, shared with the Slice website. Do not use when the user wants short video clips made from a video (start_episode does that), for YouTube, Spotify, Apple Podcasts or other web pages (they are pages, not files), for text already in the conversation, or for live audio.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	A direct https link to an audio or video file, e.g. https://example.com/episode.mp3. Not a web page.
`file`	No	An audio or video file the user attached in the conversation.
`wait`	No	Default true: wait briefly so short files come back finished. False returns at once with a transcription_id.

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes
`message`	Yes
`language`	No	Detected language code, e.g. en.
`downloads`	No
`file_name`	No
`transcript`	No	The transcript in paragraphs, with speaker labels when there is more than one voice.
`word_count`	No
`results_url`	Yes	Page with the full transcript and downloads. No sign-in; share it only with people who should see the transcript.
`duration_minutes`	No
`transcription_id`	Yes	Pass to transcription_status or email_transcript.
`transcript_truncated`	No	True when only the first part is included here; the results page has all of it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the async contract (short files finish in-call, longer ones return status "processing" plus a transcription_id), the 90-minute per-file limit, the auth/quota model (first transcript anonymous, then sign-in with 3/month shared with the website), and the return contents including speaker turns and .txt/.srt/.vtt downloads.

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?

Front-loaded with the primary use case and input forms, then limits, then exclusions. It is a dense single block and somewhat long, but nearly every sentence carries actionable information; only the downloads/return detail mildly overlaps the output schema.

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

Completeness5/5

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

For a tool with nested objects, async results, and an output schema, the description covers inputs, limits, auth, and failure/long-file behavior completely. The agent has everything needed to invoke it correctly without opening the schema.

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%, so the baseline is 3, but the description adds real meaning: it clarifies file is for user-attached media, url must be a direct media link rather than a web page, and it explains the wait semantics by describing when results come back finished versus return a transcription_id.

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 (speech in an audio/video file turned into text) plus concrete input modalities (attached file or direct https link) and the artifact produced (transcript with speaker turns and downloads). It is clearly distinguishable from siblings like start_episode and transcription_status, which it names directly.

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

Usage Guidelines5/5

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

Explicitly enumerates when to use (podcast, interview, lecture, meeting, voice note) and when not to use, naming the alternative tool (start_episode for clips) and the excluded inputs (web pages, YouTube/Spotify/Apple Podcasts URLs, text already in the conversation, live audio). Nothing about routing is left to inference.

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

All Slice 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?