Skip to main content
Glama

Delete Library content

delete_library_content
DestructiveIdempotent

Soft-deletes a Library video, guide, document, or article after the user explicitly confirms. The item leaves the Library immediately; Trainn removes the stored file later. Refuses when the item is still used by a published or draft course, as a course cover, or inside a published article. Inspect it first and pass expected_revision. confirmation_text must exactly equal DELETE LIBRARY <content_type> <content_id>, for example DELETE LIBRARY video abc123.

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": {
      "idempotency_key": "<idempotency_key>",
      "content_type": "<content_type>",
      "content_id": "<content_id>",
      "expected_revision": "<expected_revision>",
      "confirmation_text": "<confirmation_text>"
    },
    "name": "delete_library_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_idYes
content_typeYes
idempotency_keyYes
confirmation_textYesMust exactly equal DELETE LIBRARY <content_type> <content_id> after the user confirms.
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: soft-delete semantics (item disappears immediately, stored file removed later by Trainn), the exact refusal conditions, and the confirmation-text contract with a concrete example. This tells the agent what it can break and when the call will be rejected, which the destructiveHint alone does not.

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?

Four dense sentences, front-loaded with the operation and its soft-delete nature, followed by refusal rules and the confirmation contract. No filler sentences and no restatement of the title.

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?

No output schema and five required parameters on a destructive mutation, but the description covers safety, refusal, and confirmation adequately. The remaining gap is idempotency_key semantics and what a successful response contains.

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

Parameters4/5

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

Schema coverage is only 20%, so the description has to carry weight: it explains expected_revision as a concurrency token obtained via inspection and gives the exact confirmation_text template with an example. content_type values and content_id placement are derivable from the template, but idempotency_key is never explained.

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?

States a precise verb and scope: 'Soft-deletes a Library video, guide, document, or article'. 'Soft-deletes' plus the enumerated content types and the Library scope distinguish it cleanly from the course-structure deletion 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?

Gives explicit preconditions and exclusions: user must explicitly confirm, the item must not be used by a published/draft course, as a cover, or inside a published article, and 'Inspect it first and pass expected_revision' points to the inspect step. It stops short of naming inspect_library_content explicitly, so the alternative is implied rather than routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources