Skip to main content
Glama

delete_custom_tag

Deletes a custom tag from your tag library, removing it from every game that uses it. Requires confirm=true to prevent accidental deletion.

Instructions

Delete a custom tag from your tag library (it disappears from every game). Needs confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description itself discloses the destructive operation, its broad blast radius across every game, and the confirmation gate. It stops short of stating whether deletion is irreversible and whether confirm=false rejects the call, performs a dry run, or simply does nothing.

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 short statements front-load the operation, then convey its blast radius and execution requirement with no filler. Every phrase contributes tool-specific 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?

For a flat two-parameter tool with an output schema, the description supplies the target resource, global side effect, and key requirement needed to invoke it correctly. The remaining omissions—permanence, failed-confirmation behavior, and unknown-tag handling—prevent full completeness, especially without annotations.

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?

At 0% schema description coverage, the text meaningfully documents confirm by stating that it must be true, while the action supplies general target context for name. It does not explicitly say that name must identify an existing tag or define matching behavior, and it leaves the semantics of confirm=false unstated.

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 uses a specific verb and resource—"Delete a custom tag"—and locates that resource in the user's tag library. The warning that it disappears from every game clarifies its scope and distinguishes it by resource and effect from the sibling deletion tools.

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 library-wide consequence indicates that this is for removing a tag everywhere rather than making a single-game change, and "Needs confirm=true" states an invocation precondition. It does not explicitly name an alternative or warn against using the tool for a narrower removal.

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