Skip to main content
Glama

producer_generate_lyrics

Generate song lyrics from a text prompt, producing structured sections like verse, chorus, and bridge formatted for music production.

Instructions

Generate song lyrics from a text prompt.

Creates structured lyrics with proper song sections (Verse, Chorus, Bridge,
etc.) based on your description. The generated lyrics are formatted and
ready to use with producer_generate_custom_music.

Use this when:
- You need lyrics but don't want to write them yourself
- You want AI-generated lyrics for a specific theme or mood
- You need properly structured lyrics with section markers

The output includes section markers like [Verse], [Chorus], [Bridge] that
Producer's music generation understands.

Returns:
    Generated lyrics with title, status, and formatted text with section markers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of the lyrics you want. Include theme, mood, genre, and any specific elements. Examples: 'A romantic ballad about lost love and rainy nights', 'An upbeat pop song about summer vacation', 'A motivational hip-hop track about overcoming obstacles'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses output structure (section markers, title, status) and compatibility with other tools. Could add idempotency or limitation notes.

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 paragraphs, bullet list for usage, and a return section. Every sentence adds value; no fluff or redundancy.

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?

Simple tool with one parameter and output schema; description covers purpose, usage, output format, and sibling integration comprehensively.

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 description coverage is 100% with detailed examples. Description reinforces the prompt's role but adds minimal new semantic value beyond schema.

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 'Generate song lyrics from a text prompt' and specifies output includes structured sections. Differentiates from siblings like producer_generate_music (audio) and producer_cover_music.

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?

Explicitly lists three when-to-use scenarios and mentions integration with producer_generate_custom_music. Lacks explicit when-not-to-use or alternative tool comparisons.

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/AceDataCloud/ProducerMCP'

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