Skip to main content
Glama

Remove from Library

remove_from_library
DestructiveIdempotent

Take a file out of a Brand Library without deleting it. Future Briefs, Brand Edits, and Brand Skill versions stop using it; published Brand Skills keep working. Only call when the user asks.

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": {
      "brand_session_id": "<brand_session_id>",
      "media_id": "<media_id>"
    },
    "name": "remove_from_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_idYesMedia ID of the file to remove.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
brand_session_idYesBrand session ID from list_brands for the brand whose Library to use.

Output Schema

NameRequiredDescriptionDefault
idYesMedia ID of the file that was removed.
in_libraryYesAlways false: the file is no longer in the Brand Library.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description earns credit for disclosing the non-obvious blast radius: future Briefs, Brand Edits, and Brand Skill versions stop using the file while published Brand Skills keep working, and the file itself is preserved. It stops short of stating reversibility (whether add_to_library restores prior usage) or permission requirements.

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?

Three short sentences, zero filler: the scope-preserving action comes first, the downstream consequence second, and the invocation guard last. Every clause carries distinct information.

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?

An output schema exists, so return values need not be explained, and the description covers what changes downstream after removal. For a 3-parameter mutation tool this is close to sufficient; only the restoration path and any permission or multi-user implications are left unstated.

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 100%, including the pattern, format, and a note that llm_model is optional analytics-only, so the schema already carries the parameter burden. The description adds no meaning beyond it — notably it says nothing about where media_id comes from (list_library) or how brand_session_id relates to list_brands, which the schema does cover. Baseline 3 applies.

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?

"Take a file out of a Brand Library without deleting it" states a specific verb plus resource and immediately delimits it against the deletion tools in the sibling set (delete_images, delete_videos, delete_audio). An agent can distinguish this from add_to_library and from hard-delete operations without opening the schema.

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?

The description gives an explicit gating condition — "Only call when the user asks" — which is a real constraint on agent-initiated invocation, and the "without deleting it" clause signals the alternative (actual deletion) exists elsewhere. It does not name the sibling to use for permanent removal, so the routing is clear but not fully enumerated.

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