Skip to main content
Glama

remove_play_session

Deletes a specific play session by ID from Infinite Backlog, requiring confirm=true to prevent accidental removal.

Instructions

Delete one play session by id. 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>",
      "session_id": "<session_id>"
    },
    "name": "remove_play_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
confirmNo
session_idYes
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. The confirm gate is disclosed, but permanence/irreversibility, permission requirements, and the consequences of supplying collection_id are all unstated for a destructive operation.

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 action and immediately followed by the safety prerequisite. No filler, though 'by id' is imprecise when the actual key parameter is named session_id.

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 no explanation, but for a destructive 4-parameter tool with no annotations and no schema descriptions, the definition is far too thin. Half the parameters and the risk profile of deletion are left undocumented.

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%, so the description must compensate and it does not. It touches only session_id ('by id') and confirm; the required 'slug' and the optional 'collection_id' get no explanation at all.

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?

The description gives a specific verb and resource — 'Delete one play session by id' — which is sharper than the title alone. It does not, however, distinguish the tool from close siblings such as remove_play_record or remove_playthrough, whose scope differs only subtly.

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?

It states a hard prerequisite ('Needs confirm=true'), which is genuinely useful invocation guidance. It never says when to pick this over remove_play_record/remove_playthrough, nor what 'one' session implies in a collection context, so usage is only implied.

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