Skip to main content
Glama

Delete Brand

delete_brand
Destructive

Delete a brand from the caller's account. The brand stops appearing in list_brands and its Brand session ID stops working. Running brand creation, Briefs, and Reviews for it are cancelled, and its stored source files, Brand Skill files, and Review evidence are removed. These tools cannot restore a deleted brand.

Only call this when the user has explicitly asked to delete the brand. Don't infer it from a vague cleanup request — confirm which brand they mean first (use list_brands to disambiguate by name).

Args:

  • brand_session_id (string): Brand session ID from list_brands

Returns: { "brand_session_id": string, "name": string, "workspace_id": string | null, "workspace_name": string }

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand_session_id": "<brand_session_id>"
    },
    "name": "delete_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
brand_session_idYesBrand session ID from `list_brands` for the brand to delete.

Output Schema

NameRequiredDescriptionDefault
nameYesName of the deleted brand.
workspace_idYesWorkspace ID, or null for a personal workspace that has no ID.
workspace_nameYesName of the workspace that owned the brand.
brand_session_idYesBrand session ID of the deleted brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety bar is partly met — but the description goes well beyond by enumerating consequences: the brand vanishes from list_brands, its session ID becomes invalid, running creations/Briefs/Reviews are cancelled, and source files, Brand Skill files, and Review evidence are removed. It also states irreversibility ("These tools cannot restore a deleted brand"), which annotations alone do not convey.

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 safety constraint is front-loaded and the consequences follow logically; sentences are information-dense. The explicit "Returns" block is mild redundancy given a declared output schema exists, costing a point on efficiency but not clarity.

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 deletion tool, everything an agent needs is present: prerequisites, confirmation requirement, cascade effects, irreversibility, and the identifier source. With an output schema present, the description need not explain return values further, though it does so anyway.

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 description coverage is 100%, so both parameters are already documented in the schema, and the description's note ("Brand session ID from list_brands") largely restates the schema's own text. The optional llm_model analytics parameter is never mentioned in the description, though the schema explains it adequately. Baseline 3 applies where the schema carries the load.

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?

Names a specific verb and resource ("Delete a brand from the caller's account") and scopes it to the caller's account. The reader immediately knows this is a destructive removal of a brand entity, distinct from the many get_/list_/create_ siblings.

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?

Explicitly states the precondition ("Only call this when the user has explicitly asked"), the exclusion ("Don't infer it from a vague cleanup request"), and the disambiguation path (use list_brands to confirm the brand by name). This is a textbook when/when-not/alternative block for a destructive tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources