Skip to main content
Glama
Sign In

PopNow

by io.github.popnow-ai
OverviewDiscussionsAdmin

Create a song

create_music

Make an original song or instrumental track from a description. Uses site credits with OAuth or USD with an API key; the tool quotes the price.

Input Schema

NameRequiredDescriptionDefault
titleNoOptional song title, used when you give lyrics or ask for an instrumental (otherwise the song names itself).
voiceNoOptional lead singer: female or male. Leave empty to let the song decide.
lyricsNoOptional lyrics to sing. Leave empty and PopNow writes them.
promptYesThe song you want: genre, mood, instruments, what it's about. For example: upbeat summer pop about a road trip.
max_usdNoAPI key only: maximum approved USD as a decimal string with up to 9 fractional digits. Set currency to USD. Only set after the user confirms the quoted cost_usd. Never convert max_credits.
currencyNoBilling unit: USD for API keys; credits for OAuth (optional for existing OAuth clients).
max_creditsNoOAuth only: the most site credits the user agreed to spend on this. Only set it after the user confirmed a quoted price.
instrumentalNoSet true for music with no singing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Billing unit: USD for API keys; credits for OAuth (optional for existing OAuth clients).",
+  "type": "string"
+}
    • changedInput schema / properties / max_credits / description
      Previous value: -"The most credits the user agreed to spend on this. Only set it after the user confirmed a quoted price."New value: +"OAuth only: the most site credits the user agreed to spend on this. Only set it after the user confirmed a quoted price."
    • addedInput schema / properties / max_usd
      Added value: +{
+  "description": "API key only: maximum approved USD as a decimal string with up to 9 fractional digits. Set currency to USD. Only set after the user confirms the quoted cost_usd. Never convert max_credits.",
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the mutation/safety profile, and the description adds genuinely useful behavior: the operation spends credits or USD, distinguishes auth modes, and quotes a price before the agent commits. It omits whether generation is asynchronous and returns a job to poll via get_job, which is a notable remaining gap.

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 tight sentences, front-loaded with the core action and followed by the billing model. Nothing is redundant or padded.

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?

For an 8-parameter, credit-spending creation tool with no output schema, the description supplies the essential pricing and auth context. It stops short of explaining the async execution model or what the call returns, which an agent needs in a job-based sibling ecosystem.

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 coverage is 100%, so the schema already documents all eight parameters including the billing split and confirmation requirement. The description restates the OAuth/USD distinction rather than adding syntax or format detail beyond the schema, so baseline 3 applies.

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 and resource ('Make an original song or instrumental track') with the input basis ('from a description'). It clearly separates the tool from siblings such as create_sound_effects and create_speech, which produce other audio types.

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

Usage Guidelines3/5

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

Usage context is only implied through the billing sentence (credits with OAuth, USD with an API key). There is no explicit 'use this when X, use sibling Y instead' routing, even though several audio-creation siblings exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PopNow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources