Skip to main content
Glama

library_remove

Remove a media entry from your Unflick library by its ID to keep your collection up to date. Specify the entry ID to delete unwanted media.

Instructions

Remove a media entry from the library by ID

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": {
      "id": "<id>"
    },
    "name": "library_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMedia entry ID to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.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 supplied, so the description carries the full behavioral burden, and it says nothing about whether removal is permanent or reversible, whether the underlying media file is deleted from disk, or what happens if the ID does not exist. For a destructive operation with zero annotation coverage, these gaps are significant.

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?

One short, front-loaded sentence with zero wasted words. It is efficient, though its terseness is partly under-specification rather than disciplined brevity.

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?

For a no-annotation, no-output-schema destructive tool, the agent needs to know destructiveness scope, reversibility, and error behavior, none of which are covered. The definition is callable but incomplete relative to the risk involved.

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?

There is a single parameter with fully documented schema coverage (100%), so the schema already explains 'id' as the media entry ID. The description adds only 'by ID', which is essentially redundant; baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb (Remove) and resource (media entry in the library) plus the keying parameter, which is enough to distinguish it from siblings that remove bookmarks, playlists, or scripts. It stops short of any explicit sibling differentiation, so it is clear but not maximally so.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus library_search, library_list, or cleanup, and no mention of prerequisites or exclusions. The agent must infer entirely from the name and description that this is the deletion counterpart to library_list.

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

Deploy Server

Other Tools