Skip to main content
Glama

delete_highlight

Destructive

Removes a CS2 highlight definition while keeping its rendered videos, so you can clean up highlight specs without deleting generated outputs.

Instructions

Delete a highlight definition (its rendered videos are kept).

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

Input Schema

NameRequiredDescriptionDefault
highlight_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: rendered videos are kept, which tells the agent the blast radius is limited to the definition. It stops short of covering irreversibility, confirmation needs, or behavior when the ID is unknown.

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?

A single front-loaded sentence with a parenthetical that carries the most decision-relevant detail. Nothing is wasted, though the parenthetical could be a standalone clause for cleaner scanning.

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?

With annotations covering the safety profile and an output schema present, the remaining burden is behavioral, and the description answers the main question (are renders affected). Only edge-case behavior on invalid or already-deleted IDs is left unaddressed.

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 0%, and the description says nothing about highlight_id, so it does not fully compensate. The parameter name is self-explanatory and the description's framing ties the operation to a definition, which is mild added meaning, but format/validation expectations remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Delete a highlight definition") and clarifies the scope of what is removed versus retained. It distinguishes deletion of the definition from the rendered artifacts, which is the key ambiguity for this operation. Sibling differentiation is only implicit, but the parenthetical does most of the disambiguating work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the word "Delete" — an agent can infer this is the removal path for a highlight. However, there is no explicit guidance on when to use this versus siblings like cancel_job (stopping a job) or render_highlight, and no stated prerequisites such as whether the highlight must be unrendered or idle first.

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