Skip to main content
Glama

Add the file to a song import

add_song_import_audio

Give the audio of a released song Kinetune couldn’t fetch The song is made from the file with the release’s title and cover (MP3, WAV or M4A up to 250 MB), and analyzed. For a failed import (or one still queued).

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": {
      "import_id": "<import_id>"
    },
    "name": "add_song_import_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
audio_urlNoA public https URL of the song’s audio (a file on your computer: create_upload, then its file_url)
import_idYesThe import id (import_…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent, open-world mutation. The description adds real behavioral context beyond that: supported formats (MP3, WAV, M4A), a 250 MB size limit, and the consequence that a song is created from the file using the release's title and cover and then analyzed. It does not say what happens on repeated calls or what the response contains, which is the main remaining gap.

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?

It is short and front-loads the action, but it is essentially one run-on sentence with a missing period after "fetch," forcing the reader to re-parse where the purpose ends and the behavior explanation begins. The size and format limits are useful, but the delivery is sloppy.

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 two-parameter mutation with full schema coverage and annotations, the description covers the essential what and when. It omits the outcome of the call (what the import or song looks like afterward) and any note that repeated calls will not be idempotent despite creating a song, which an agent would want before retrying.

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 both parameters are already documented, including that audio_url must be a public https URL obtainable via create_upload. The description still adds meaning the schema lacks — accepted audio formats and the 250 MB ceiling for audio_url, plus the fact that import_id must reference a failed or queued import.

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 action and resource: supply an audio file for a song import. It also scopes the action to imports that failed or are still queued and to a released song Kinetune could not fetch. The wording is grammatically broken ("couldn't fetch The song is made..."), which slightly muddies the read, but the purpose is still discernible.

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

Usage Guidelines3/5

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

The closing phrase "For a failed import (or one still queued)" gives an implicit condition for use, and the schema description points to create_upload as the way to obtain the audio_url. However, no sibling is named or excluded, and there is no statement about what to do with a successful import or a cancelled one, so the routing is inferred rather than explicit.

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.

Resources