Skip to main content
Glama

Generate lyrics

generate_lyrics

Write song lyrics from a description, without generating audio. Useful as a first step before generate_music with custom=true, so the user can approve the words before paying for audio. Asynchronous — poll with get_task.

Input Schema

NameRequiredDescriptionDefault
promptYesDescription of the lyrics to write, e.g. 'a love song about meeting someone at a coffee shop'.
providerNoMusic backend: 'suno' (default) or 'producer'.
lyrics_modelNoLyrics model: classic or remi.
wait_secondsNoPoll server-side for up to this many seconds (max 240). Lyrics usually finish in under 30 seconds.

Output Schema

NameRequiredDescriptionDefault
rawNoFull result payload when completed — clip IDs, lyrics text and per-clip metadata. Clip IDs from here are what extend_music takes.
noteYesWhat to do next.
statusYesOne of: queued, in_progress, completed, failed.
task_idYesPass this to get_task together with platform to check progress.
platformYes'suno' or 'producer'. Pass to get_task.
audio_urlsNoFinished audio URLs, when the task completed within wait_seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the mutation/safety profile (readOnlyHint=false, destructiveHint=false). The description adds valuable behavioral context beyond annotations: it is asynchronous and requires polling with get_task, and it produces lyrics only, not audio. No contradictions with annotations.

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 sentences with no redundancy: core function first, then the primary use case and user-benefit context, then the async behavior. Every sentence earns its place and the structure is immediately scannable.

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?

Complete for an async lyric-generation tool. With an output schema present, return values do not need explanation. The description covers purpose, distinction from audio generation, integration with generate_music, and polling behavior, so an agent has what it needs to invoke correctly.

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?

Input schema coverage is 100%, so all parameters and their meanings are already documented. The description does not add parameter-level detail beyond the schema, so the baseline 3 applies. No compensation needed.

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?

States a specific verb ('Write') and resource ('song lyrics from a description'), and explicitly differentiates from audio generation with 'without generating audio'. It also names the related sibling generate_music, making the tool's scope immediately clear.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: as a first step before generate_music with custom=true, so users can approve lyrics before paying for audio. It also implicitly tells when not to use it (when audio is needed) and points to the async flow with get_task.

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