Skip to main content
Glama

Car Background AI

Delete custom background

delete_background
Destructive

Permanently delete one of the workspace's custom backgrounds, e.g. a scene the user no longer wants in their list. It cannot be undone through this server; a deleted scene has to be made again with create_background. Photos already generated with it are not affected, and no credits are charged or refunded. Only custom backgrounds (custom: true in list_backgrounds) can be deleted, never built-in ones. To change a scene instead of removing it, use refine_background. Returns the id with deleted: true, or not_found for an unknown id.

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": {
      "background_id": "<background_id>"
    },
    "name": "delete_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
background_idYesThe `id` of a custom background.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint/readOnlyHint) by disclosing irreversibility, the required recovery path (recreate with create_background), that existing generated photos are unaffected, that no credits are charged or refunded, and the return shape including a `not_found` case.

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?

Front-loads permanence and resource scope, then layers constraints and alternatives. Dense but nearly every clause carries information; the parenthetical example ("e.g. a scene the user no longer wants in their list") is the only mildly expendable fragment.

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 single-parameter destructive tool with no output schema, everything an agent needs is present: eligibility rules, irreversibility, credit implications, alternative tools, and return values. No gaps remain.

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%, so the baseline applies, but the description adds real meaning: the `background_id` must refer to a custom background (`custom: true`), never a built-in one, and an unknown id yields `not_found`. Slight gain over the schema's bare "id of a custom background".

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 ("Permanently delete one of the workspace's custom backgrounds") and scopes it to custom backgrounds only. It is clearly distinguishable from create_background and refine_background, which are named in the text.

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 covers when to use (a scene the user no longer wants), when not to ("To change a scene instead of removing it, use refine_background"), what cannot be deleted (built-in backgrounds), and how to verify eligibility via `custom: true` in list_backgrounds.

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