Skip to main content
Glama

suno_get_lyric_format_guide

Learn how to format lyrics for Suno music generation using section markers to guide song structure and improve melody generation.

Instructions

Get guidance on formatting lyrics for Suno music generation.

Shows how to structure lyrics with section markers for best results.
Following this format helps Suno understand the song structure and
generate appropriate melodies for each section.

Returns:
    Complete guide with section markers, examples, and tips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function decorated with @mcp.tool() that returns a comprehensive guide on formatting lyrics for Suno music generation, including section markers, example structure, and tips.
    @mcp.tool()
    async def suno_get_lyric_format_guide() -> str:
        """Get guidance on formatting lyrics for Suno music generation.
    
        Shows how to structure lyrics with section markers for best results.
        Following this format helps Suno understand the song structure and
        generate appropriate melodies for each section.
    
        Returns:
            Complete guide with section markers, examples, and tips.
        """
        # Last updated: 2026-04-05
        return """Lyric Format Guide for Suno:
    
    Section Markers (use square brackets):
    - [Verse] or [Verse 1], [Verse 2]: Main storytelling sections
    - [Chorus]: Repeated catchy section (the hook)
    - [Pre-Chorus]: Build-up before chorus
    - [Bridge]: Contrasting section, usually near the end
    - [Outro]: Ending section
    - [Intro]: Opening instrumental or vocals
    
    Example Structure:
    ```
    [Verse 1]
    First verse lyrics here
    Setting up the story
    
    [Pre-Chorus]
    Building anticipation
    Leading to the hook
    
    [Chorus]
    The main hook goes here
    Most memorable part
    Repeat this section
    
    [Verse 2]
    Second verse continues
    The narrative unfolds
    
    [Chorus]
    The main hook goes here
    Most memorable part
    Repeat this section
    
    [Bridge]
    Something different here
    A twist or climax
    
    [Chorus]
    The main hook goes here
    Most memorable part
    Final repetition
    
    [Outro]
    Winding down
    Fade out
    ```
    
    Tips for Best Results:
    - Keep lines concise (4-8 words) for better singing flow
    - Use simple, clear language that's easy to sing
    - Include rhymes for catchiness (especially in chorus)
    - Leave some creative freedom for the AI
    - Use consistent line lengths within sections
    - End verses with a lead-in to the chorus
    """
  • main.py:303-305 (registration)
    The tool registration entry in main.py listing the tool name and description as part of the available tools.
        "name": "suno_get_lyric_format_guide",
        "description": "Get lyrics formatting guide",
    },
  • Reference to the tool in the suno_list_actions description within the same file.
    - suno_get_lyric_format_guide: Show how to format lyrics
  • Imports the mcp server instance which provides the @mcp.tool() decorator used to register the tool.
    """Informational tools for Suno API."""
    
    from core.server import mcp
  • main.py:140-140 (registration)
    The tool is listed in the safe_print output showing available tools.
    safe_print("    - suno_get_lyric_format_guide")
Behavior4/5

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

No annotations are provided, but the description discloses that the tool returns a guide with section markers, examples, and tips. It is clearly a read-only, informational tool with no side effects, which is transparent enough for an agent.

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?

The description is three sentences: purpose, practical benefit, and return contents. It is front-loaded and concise with no redundant information.

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?

Given no parameters and an output schema, the description adequately explains the tool's purpose and return value. It could mention that no input is required, but the schema already implies that. Overall sufficient for an agent to understand 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?

The tool has no parameters, so the description need not add parameter details. The baseline for 0 parameters is 4, and the description appropriately focuses on what the tool does and returns.

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?

The description clearly states 'Get guidance on formatting lyrics for Suno music generation,' specifying the action (get) and resource (lyric formatting guide). It distinguishes itself from sibling tools that generate or manipulate music/lyrics, such as suno_generate_lyrics.

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?

The description explains that using this guide helps structure lyrics with section markers for best results, implying it should be used before generating music with custom lyrics. While it doesn't explicitly state when not to use it, the context of siblings makes its purpose self-evident.

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/SunoMCP'

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