Skip to main content
Glama

remove_play_record

Delete a single Play Records row by 1-based row_index, or clear the entire category when row_index is empty and confirm is true.

Instructions

Remove one row (row_index, 1-based) from a Play Records category, or the whole category when row_index is empty (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>",
      "category": "<category>"
    },
    "name": "remove_play_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
confirmNo
wait_msNo
categoryYes
row_indexNo
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / wait_ms / default
      Previous value: -3000New value: +0
  2. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and does disclose that this is a destructive removal, that row_index is 1-based, and that whole-category deletion is gated behind confirm=true. It omits whether deletion is reversible, whether confirm is required or ignored for single-row mode, and any permission or side-effect details for a mutation tool.

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?

A single sentence with zero filler, front-loading the primary action and appending the conditional bulk-delete rule and its guard. Every clause carries actionable information.

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

Completeness3/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 explained, and the core removal semantics are covered. However, for a six-parameter destructive tool with no annotations, leaving slug, collection_id, and wait_ms undescribed is a meaningful completeness gap.

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 there are six parameters, so the description must compensate and only partly does: it explains row_index (1-based, empty = whole category) and implies confirm's role. Three parameters, including collection_id and wait_ms, are left entirely undocumented in both schema and description.

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 names a specific verb (Remove) and resource (one row from a Play Records category), and distinguishes two distinct operations: single-row removal and whole-category removal. It is clear enough to separate from set_play_record_category or remove_play_session, though it does not explicitly name those siblings.

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?

It gives an explicit rule for selecting between the two modes: row_index present means remove one row, row_index empty means remove the whole category, and that path requires confirm=true. It does not state when to prefer a different removal tool, so no exclusion guidance is present.

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