Skip to main content
Glama

remove_playthrough

Delete a playthrough and every session tied to it, requiring confirm=true to guard against accidental removal.

Instructions

Delete a playthrough and all its sessions. 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": {
      "slug": "<slug>",
      "playthrough": "<playthrough>"
    },
    "name": "remove_playthrough"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
confirmNo
playthroughYes
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the important cascade (all sessions are destroyed) and the confirm gate, but says nothing about irreversibility, required permissions, or what happens to related records such as play records or collection membership.

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?

Two short sentences, front-loaded with the destructive action and its scope, then the confirm requirement. No wasted wording, though the second sentence is terse to the point of omitting needed detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. But for a destructive, unannotated tool with four undocumented parameters, the definition leaves too much unspecified — particularly collection_id and whether the deletion is recoverable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description only clarifies one of them (confirm must be true). The meaning of slug, playthrough, and especially collection_id — which is optional with an empty default — is left entirely unexplained.

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 and resource plus the cascade scope: 'Delete a playthrough and all its sessions.' The cascade detail distinguishes it from the sibling remove_play_session, which presumably deletes a single session, so an agent can tell them apart without opening schemas. It stops short of naming the alternative explicitly.

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?

'Needs confirm=true' gives a hard prerequisite for invocation, which is useful. However, there is no guidance on when to choose this over remove_play_session or remove_play_record, and no statement of when not to use it.

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