Skip to main content
Glama

suno_delete_persona

Permanently deletes a saved artist persona to remove unused or outdated voice profiles. This action is irreversible.

Instructions

Delete a saved artist persona.

Permanently removes a previously created persona. This action cannot be undone.

Use this when:
- You want to remove an unused voice persona
- You need to clean up old personas
- You want to delete a persona you no longer need

Returns:
    Confirmation of the deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persona_idYesThe persona ID to delete.
user_idNoThe user ID for ownership verification (optional).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the suno_delete_persona tool. Decorated with @mcp.tool(), it accepts persona_id (required) and user_id (optional), calls client.delete_persona(), and returns the result as JSON.
    @mcp.tool()
    async def suno_delete_persona(
        persona_id: Annotated[
            str,
            Field(description="The persona ID to delete."),
        ],
        user_id: Annotated[
            str | None,
            Field(description="The user ID for ownership verification (optional)."),
        ] = None,
    ) -> str:
        """Delete a saved artist persona.
    
        Permanently removes a previously created persona. This action cannot be undone.
    
        Use this when:
        - You want to remove an unused voice persona
        - You need to clean up old personas
        - You want to delete a persona you no longer need
    
        Returns:
            Confirmation of the deletion.
        """
        payload: dict = {"persona_id": persona_id}
        if user_id:
            payload["user_id"] = user_id
    
        result = await client.delete_persona(**payload)
        return json.dumps(result, ensure_ascii=False, indent=2)
  • The HTTP client method that performs the actual API call. Sends a DELETE request to /suno/persona with persona_id (and optional user_id) as query parameters.
    async def delete_persona(self, **kwargs: Any) -> dict[str, Any]:
        """Delete a persona."""
        persona_id = kwargs.get("persona_id", "")
        logger.info(f"🗑️ Deleting persona: {persona_id}")
        url = f"{self.base_url}/suno/persona"
        params = {k: v for k, v in kwargs.items() if v is not None}
        async with httpx.AsyncClient() as http_client:
            try:
                response = await http_client.delete(
                    url,
                    params=params,
                    headers=self._get_headers(),
                    timeout=self.timeout,
                )
                if response.status_code >= 400:
                    self._handle_error_response(response)
                return response.json()  # type: ignore[no-any-return]
            except SunoError:
                raise
            except Exception as e:
                logger.error(f"❌ Request error: {e}")
                raise SunoAPIError(message=str(e)) from e
  • main.py:278-281 (registration)
    Registration of suno_delete_persona in the tools list within the server card response (used for MCP discovery/handbook registration).
    {
        "name": "suno_delete_persona",
        "description": "Delete a saved voice persona",
    },
  • main.py:131-131 (registration)
    The tool name is printed in the CLI help/tool listing (the 'safe_print' listing of available tools).
    safe_print("    - suno_delete_persona")
  • The input schema is defined inline via Pydantic Field annotations on the function parameters: persona_id (required str) and user_id (optional str).
    async def suno_delete_persona(
        persona_id: Annotated[
            str,
            Field(description="The persona ID to delete."),
        ],
        user_id: Annotated[
            str | None,
            Field(description="The user ID for ownership verification (optional)."),
        ] = None,
Behavior3/5

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

The description states that the action 'cannot be undone' and 'Permanently removes', indicating destructive behavior. No annotations are provided, so the description carries the full burden. It does not disclose permissions, side effects, or constraints beyond irreversibility.

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 concise, with a clear title, a one-sentence summary, bulleted usage guidelines, and a return statement. It is front-loaded and contains no unnecessary 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?

The description covers the essential aspects of a delete operation: what it does, irreversibility, usage scenarios, and return value. It does not detail error handling or prerequisites, but for a simple delete with an output schema mentioning confirmation, it is sufficiently complete.

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?

The input schema covers 100% of parameters with descriptions. The description lists 'persona_id' and 'user_id' without adding new meaning beyond what the schema already provides. Thus, the description adds no additional parameter semantics.

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 the verb 'delete' and the resource 'saved artist persona'. It explicitly says 'Permanently removes a previously created persona.' This distinguishes it from sibling tools like 'suno_create_persona' and 'suno_list_personas'.

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 provides a list of explicit use cases ('Use this when: ...'), which helps the agent decide when to invoke this tool. However, it does not mention when not to use it or suggest alternatives.

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