How to Write Lyrics for Mureka

The lyrics field is the one input Mureka will not let you skip. In its song generation API, lyrics is a required field. The style prompt is optional. That ordering tells you where the weight sits.

This post is about what to put in that field. Mureka's documented limits and workflow come from its own pages. The craft parts, the meter and section habits, come from my Suno runs, and I will say so each time rather than dressing up guesses as test results.

What Mureka documents about the field

Three facts worth having in front of you.

The lyrics field accepts up to 5000 characters. That is a generous ceiling. A three or four minute song with full verses, a chorus repeated three times, and a bridge usually lands well under half of it.

Custom mode supports structured output with verse, chorus, and bridge tags, according to Mureka's Knowledge base, and every lyric example in Mureka's API docs is written with bracketed section tags. Their quickstart lyric block opens with [Verse]. Their lyric continuation example opens with [Pre-chorus]. Their song extension example opens with [Intro].

There are dedicated endpoints for writing lyrics from a prompt and for continuing existing lyrics. In the web app, the same functions appear as Generate Lyrics and Optimize buttons next to the lyrics area. If you have half a song, the continuation path exists specifically for that.

One thing I will not tell you: whether Mureka acts on ad-lib cues in parentheses, or on vocal-style tags. Its docs describe verse, chorus, and bridge structure tags and nothing more granular, so anything past that would be me guessing. I use ad-libs heavily on Suno. I do not assert them here.

The shape of a sheet

Start with the section plan before any words. Something like intro, verse, chorus, verse, chorus, bridge, chorus. Write the labels first, in brackets, on their own lines, with a blank line above each. It looks over-organised and it takes thirty seconds.

Then fill the sections in this order: chorus first, then verse one, then verse two against verse one, then the bridge. The chorus is the part that repeats, so it is the part worth writing well, and every other section has to sit next to it without embarrassing itself.

Keep one section per block. Do not run two verses together under a single tag and expect the model to find the seam.

Meter, which is the part that actually matters

Here is the thing I would tell anyone starting out, and it is from my own Suno work rather than from any Mureka page.

Sections that share a melodic slot need to share a rough syllable count. Verse one and verse two get sung to the same melody. If verse one runs nine syllables a line and verse two runs nineteen, the second one has to be crammed into a space shaped for the first, and the phrasing goes with it.

You do not need to count precisely. Get within a syllable or two, line for line, and read both verses out loud back to back. If one of them makes you rush or run out of breath, that is your answer.

Stress matters more than raw count, which is the part that took me longest to accept. Two lines can have the same number of syllables and sit completely differently, because English does not distribute emphasis evenly. Tapping the beat while you read the line catches this in about four seconds and no amount of counting on your fingers ever will.

There is no reason any of this would be Suno-specific. It is a consequence of fitting a variable number of words to a repeating melody, which is a problem every one of these models has.

Before and after

Before, lyrics:

[Verse]
I found your handwriting on the back of a receipt in the glovebox this morning and it took me right back to the summer we spent driving to nowhere in that terrible car

[Chorus]
Ghost in the glovebox

[Verse]
Rain
The wipers are broken again
I never fixed anything you asked me to fix and now there is nobody left to ask

Before, style prompt:

emotional indie song, powerful vocals, atmospheric, nostalgic, beautiful, high quality production

The tags are there, which is more than most first drafts, but nothing else is working. Verse one is over forty syllables in a single run. Verse two opens with a one-word line and closes with a twenty-two syllable one. The chorus is three words with no repetition and nothing to hold on to. And the style prompt is six compliments and one genre.

After, lyrics:

[Verse 1]
Found your handwriting on a receipt
Folded in the glovebox door
That summer we drove out to nowhere
In a car that barely made it

[Chorus]
Ghost in the glovebox, ghost in the rain
Ghost in the songs I still can't play
Ghost in the glovebox, ghost in the rain
Nothing I fixed and nothing I said

[Verse 2]
Rain is coming through the window
Wipers broke again last winter
You asked me once to fix them
There's nobody left to ask

[Bridge]
I keep the receipt in the same place
I keep the car in the same place
I keep meaning to move both

After, style prompt:

indie folk rock, mid tempo around 88 bpm, acoustic guitar, brushed drums, upright bass,
restrained female vocal, close dry mix, light room reverb

Verse one and verse two now sit within a syllable or two of each other, line for line, around seven to nine each. The chorus repeats its first line, which does more for a hook than any amount of clever wording, and it has four lines instead of three words. The bridge deliberately breaks the pattern with three shorter lines, because that is what a bridge is for.

The style prompt stopped grading the song and started describing it: one genre, a tempo with a number, three instruments, a vocal delivery, two mix decisions. On Mureka the vocal gender can also go in its own dedicated field, so the prompt does not have to carry it.

Practical notes

• Leave the model on auto. Mureka describes it as selecting the latest version of the regular model, which is the sane default unless you have a specific reason.
• Mureka's docs say a request generates two songs by default, up to three. Budget for hearing more than one take.
• If a single line comes back wrong, Mureka documents a fine-tune editing mode that regenerates individual lines the model mis-sang, with an option to keep the existing melody. That is cheaper than rerolling the whole song for one bad phrase.
• Instrumentals have their own endpoint that takes no lyrics at all, so do not fight the lyrics field for an instrumental idea.

Why I built Mugical

Everything above is maybe twenty minutes of work per song, done by hand, before you hear a single note. I did it enough times that I wrote a tool to take the mechanical half off me. You give Mugical a song idea plus genre, mood, instrumentation and era, and it returns a sheet with the sections tagged and the ad-lib cues placed, next to a style prompt covering genre, instruments, mood, tempo and vocal style. The meter pass, evening verse two up against verse one, is still yours. That is the part I am working on next.

It does not generate audio. That still happens wherever you paste the output. What it produces is the text those platforms sing.

You can try it on a song idea and see the tagged sheet it hands back. The style prompt half of the job has its own post, how to structure a Mureka style prompt. And if you also work in Suno and want to keep one sheet for both, I wrote about what changes between Mureka and Suno formatting.