Skip to main content
Glama
hermoso-ai

Hermoso

Official

Delete a brand workspace

delete_brand
DestructiveIdempotent

Permanently delete a brand workspace and all its contents—profiles, assets, and connected accounts—with a two-step confirmation to prevent accidental loss.

Instructions

PERMANENTLY delete a brand workspace and EVERYTHING in it — brand profile, memory, swipefile, Library creations, generated assets, avatars, skills, playbooks, chats — and disconnect its connected accounts. Irreversible, and it applies to everyone the workspace is shared with. Call it WITHOUT confirm first: it reports exactly what that workspace holds. Show the user that inventory verbatim, get an unambiguous yes, then call again with confirm:true — plus, if the workspace is not empty, confirmName set to its exact name and confirmConnectors set to the number of connected accounts it reported. Those two exist because confirming INTENT does not prove you picked the right WORKSPACE, and a wrong target is how a live brand was destroyed. The account's FIRST/anchor brand cannot be deleted this way (it holds the workspace's root storage) — that one is replaced from the app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYesbrand id or exact name from list_brands
confirmNoREQUIRED true — this destroys the whole workspace and cannot be undone
confirmNameNothe workspace's EXACT name, required when it is not empty — copy it from the inventory this tool returned, after the user has agreed to it
confirmConnectorsNothe number of connected accounts the inventory reported, required when there is at least one — the user must specifically agree to losing them, because reconnecting each needs a browser and no agent can do it
Behavior5/5

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

Annotations already mark destructiveHint=true, but the description adds crucial behavioral context: the operation is irreversible, affects all shared users, requires a confirmation protocol, and the first call without confirm serves as a dry-run inventory. It explains the rationale for the confirmation fields, going well beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence carries necessary safety information. It is front-loaded with the most critical warning (irreversible) and then flows logically into the confirmation protocol. Though it is a long paragraph, it is structured in a cause-and-effect manner that justifies its length. Could be broken into shorter sections, but it is not bloated.

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?

For a destructive, high-stakes operation, the description covers the full behavioral contract: what is deleted, irreversibility, impact on shared users, the two-phase confirmation with exact parameters, and the anchor-brand exception. Nothing essential for an agent to call it correctly is missing.

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?

Schema coverage is 100% and each parameter already has a description. The description adds value by explaining why confirmName and confirmConnectors exist: to prove the correct workspace was targeted, preventing accidental destruction of a live brand. This clarifies the intent and requirement beyond schema descriptions.

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 states a specific verb and resource: "PERMANENTLY delete a brand workspace and EVERYTHING in it." It enumerates what is included and explicitly distinguishes this from other delete tools by naming the anchor-brand exception. The purpose is unmistakable.

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?

The description gives an explicit two-phase workflow: call without confirm to get an inventory, show the user, get unambiguous yes, then call with confirm:true and necessary verification fields. It also states when NOT to use it (anchor brand) and how that case is handled. This is exemplary usage guidance.

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/hermoso-ai/hermoso'

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