Skip to main content
Glama

generate_custom_song

Generate custom songs by specifying title, lyrics, and music style. Use when users provide detailed song information including complete lyrics.

Instructions

🎵 Custom Mode: Generate songs based on detailed song information (user specifies song name, lyrics, style, etc.)

Use case: Use when users provide detailed song information including song name, complete lyrics, and style.

Example inputs:
- "Song name: Summer of Cicada Shedding, Lyrics: [complete lyrics], style: folk"

⚠️ COST WARNING: This tool makes an API call to MusicMCP.AI which may incur costs (5 credits per generation). Each generation creates 2 songs. Only use when explicitly requested by the user.

Language Note: Pass the title and lyrics in the user's input language.

Args:
    title (str): Song title, required
    lyric (str, optional): Complete lyrics content, not required when instrumental is True
    tags (str, optional): Music style tags (e.g., 'pop', 'rock', 'folk')
    instrumental (bool): Whether instrumental only (no lyrics)

Returns:
    Song information including download URLs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
instrumentalYes
lyricNo
tagsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses API call, cost (5 credits), creates 2 songs, and language note. No annotations provided, so description carries full burden and does it well.

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?

Well-structured with sections, front-loaded purpose. Slightly lengthy but every sentence adds value. Could be more concise but still effective.

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?

Covers inputs, cost, language, and output (download URLs). Output schema exists but description provides additional context. Complete enough for usage.

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 description coverage is 0%, but description adds meaning: explains each param, optionality, condition (lyric not required if instrumental). Good compensation.

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?

Clearly states it generates songs based on detailed information, with examples. Distinguishes from sibling 'generate_prompt_song' by emphasizing detailed song info.

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?

Provides when-to-use guidance (user provides detailed info), cost warning, and explicit condition 'Only use when explicitly requested'. Does not contrast with sibling tool though.

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/fastmcp-me/aimusic-mcp-tool'

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