Skip to main content
Glama
Sign In

ViralMint

by net.viralmint
OverviewDiscussionsAdmin

Use a Library song

song_from_library

Free. Makes a Music Video song from an audio file in your web Library (a video isn't accepted). rights_confirmed: true only when the user has told you they own this song or have permission to use it. It does not read the song: call song_analyze next. Captions on a song are always whole lines (never word sync).

Args: library_id: an audio item from library_list. rights_confirmed: must be true (see above).

Returns: {ok, song_id, size}

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": {
      "library_id": "<library_id>",
      "rights_confirmed": "<rights_confirmed>"
    },
    "name": "song_from_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
library_idYes
rights_confirmedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing cost (free), the fact that it does not read/analyze the song, the required follow-up call to song_analyze, and a caption behavior limitation (always whole lines, never word sync). These are non-obvious traits an agent could not infer from structured fields.

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-loads the key fact ('Free.') and uses a clean Args/Returns structure with no wasted sentences. Slightly verbose in the rights_confirmed explanation, but every element is functional.

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?

There is no output schema, and the description compensates by listing the return shape {ok, song_id, size}. Combined with the input constraints and next-step guidance, an agent has everything needed to invoke this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it does: library_id is constrained to an audio item from library_list, and rights_confirmed is explained as requiring explicit user confirmation of ownership or permission. It adds meaning the schema's pattern/const alone cannot convey.

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?

States a specific verb and resource: 'Makes a Music Video song from an audio file in your web Library', and explicitly excludes video inputs. It does not distinguish itself from similar siblings such as studio_create_from_audio or music_video_create, so it stops short of full sibling differentiation.

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 operational context: it is free, only audio (not video) is accepted, library_id must come from library_list, and song_analyze should be called next. It lacks an explicit 'when not to use this' beyond the video exclusion, but the workflow guidance is strong.

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

All ViralMint toolsInspect
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