Skip to main content
Glama

upload_audio

Free. Step 1 of adding the user's own audio file to their library: returns a one-time upload URL (valid 10 minutes). PUT the file there, then call save_upload. Only upload audio the user owns or has rights to.

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": {
      "contentType": "<contentType>",
      "size": "<size>"
    },
    "name": "upload_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYesExact file size in bytes (max 50 MB). The upload is rejected if the size differs.
contentTypeYesMIME type, e.g. audio/mpeg, audio/wav, audio/mp4, audio/flac, audio/ogg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Only destructiveHint=false is supplied, so the description usefully adds that the call is 'Free', that the returned URL is one-time and expires in 10 minutes, that a PUT is required before continuing, and a rights constraint on the content. It does not say what happens if the URL expires or the upload is rejected, and no re-request flow is described.

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?

Three short sentences, cost and step position front-loaded, followed by the action sequence and the constraint. Every sentence carries distinct, actionable information.

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 two-parameter tool with no output schema, the description explains the return value (one-time URL plus its validity), the required follow-up call, and the cost model. Nothing an agent needs in order to invoke it correctly is missing.

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%, so contentType and size are already fully documented, including the 50 MB maximum and the size-mismatch rejection. The description adds no parameter-level detail beyond the schema, so the baseline of 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?

The description names a specific action and resource ('Step 1 of adding the user's own audio file to their library') and states the concrete output (a one-time upload URL). It also distinguishes itself from the sibling save_upload by framing itself as the earlier step.

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?

It clearly establishes the multi-step context: request the URL here, PUT the file, then call save_upload. What is missing is explicit guidance on when to use this versus other ways of getting audio into the library (e.g. generate_music), but within its own workflow the sequencing is unambiguous.

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.