Skip to main content
Glama

Delete a brand asset

delete_brand_asset
Destructive

Removes one image from a brand's stored images for good. Returns deleted, and storage_deleted, which reports whether the underlying file was removed as well; file cleanup can fail separately. Not reversible: the image would have to be uploaded again.

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": {
      "asset_id": "<asset_id>"
    },
    "name": "delete_brand_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYesBrand image id from list_brand_assets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "https://json-schema.org/draft/2020-12/schema",
      -  "additionalProperties": false,
      -  "properties": {
      -    "asset_id": {
      -      "anyOf": [
      -        {
      -          "description": "asset id value in this response.",
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "asset id value in this response."
      -    },
      -    "deleted": {
      -      "anyOf": [
      -        {
      -          "description": "deleted value in this response.",
      -          "type": "boolean"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "deleted value in this response."
      -    },
      -    "storageDeleted": {
      -      "anyOf": [
      -        {
      -          "description": "storageDeleted value in this response.",
      -          "type": "boolean"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "storageDeleted value in this response."
      -    },
      -    "storage_deleted": {
      -      "anyOf": [
      -        {
      -          "description": "storage deleted value in this response.",
      -          "type": "boolean"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "storage deleted value in this response."
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  2. Changed1 schema field changed
    • changedInput schema / properties / asset_id / description
      Previous value: -"Brand image reference from list_brand_assets."New value: +"Brand image id from list_brand_assets."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so irreversibility is partly covered; the description adds genuinely new behavior by disclosing the return fields (deleted, storage_deleted) and that underlying file cleanup can fail independently of the record deletion.

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: the destructive action and permanence come first, then the return-value nuance. No filler or repetition of the title.

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 a one-parameter destructive call with annotations covering the safety profile and no output schema, the definition supplies what an agent needs: permanence, partial-failure semantics, and the shape of the response. Only peripheral details like auth requirements are absent.

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% and the single asset_id parameter is already documented with its source (list_brand_assets). The description adds no further meaning about the identifier, so the 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 with scope ('Removes one image from a brand's stored images'), which distinguishes it from sibling mutations such as update_brand_asset or set_primary_brand_asset that act on the same object without removing it.

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?

Gives decision-relevant context: the deletion is permanent and the image would have to be re-uploaded. It does not name an alternative tool or state explicit preconditions, but the irreversibility warning is enough to steer usage.

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.