Skip to main content
Glama

Get audio URL

get_audio_url

Retrieve a temporary streaming URL for a submission's native audio, with HTTP Range support for efficient playback.

Instructions

Get a short-lived presigned URL to a submission's full native audio (supports HTTP Range). Use for streaming; for a durable snippet to embed in a lesson, use get_audio_clip instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
submission_idYesThe submission id.
Behavior4/5

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

Description discloses that the URL is short-lived and supports HTTP Range, which helps with streaming. However, the exact lifetime is not specified, which could be important.

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

Conciseness5/5

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

Two sentences, front-loaded with core action, no wasted words.

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?

Given one parameter and no output schema, the description adequately explains the return value and use case. Slight gap on URL duration, but overall complete.

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?

Sole parameter submission_id is fully described in the schema. The description adds no extra meaning beyond what the schema provides, so baseline score 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?

The description clearly states the tool gets a short-lived presigned URL for a submission's full native audio, and explicitly distinguishes it from the sibling get_audio_clip tool.

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 tells when to use this tool (for streaming) and when not (for durable snippets), directing users to the alternative get_audio_clip.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lingochunk/lingochunk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server