Skip to main content
Glama

remove_from_collection

DestructiveIdempotent

Take items out of a collection; the items themselves are kept. Example: collection_id, item_ids=[""].

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": {
      "collection_id": "<collection_id>",
      "item_ids": "<item_ids>"
    },
    "name": "remove_from_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy, for the change history
item_idsYesItem ID or array of IDs
collection_idYesCollection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / collection_id / description
      Previous value: -"The collection ID"New value: +"Collection ID"
    • changedInput schema / properties / item_ids / description
      Previous value: -"Item ID or array of item IDs to remove"New value: +"Item ID or array of IDs"
    • changedInput schema / properties / item_ids / oneOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "maxItems": 20,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / reason / description
      Previous value: -"Why this change was made (shown to user in change history)"New value: +"Why, for the change history"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already disclose a mutating, destructive, idempotent operation. The description adds the crucial scope of that destructiveness: collection membership changes while the underlying items are kept, so there is no contradiction with destructiveHint. It does not add response, error, permission, or history behavior.

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?

It is compact and front-loads both the action and the key non-deletion caveat. The example earns its place but is sketchy because collection_id is named without a value, preventing a top score.

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?

For a simple three-parameter membership mutation, the operation, preservation behavior, example, complete schema, and annotations are sufficient for basic invocation. Explicit alternatives and result/error behavior remain absent, so it is helpful rather than comprehensive.

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?

With 100% schema description coverage, the baseline is 3. The example reinforces the two required arguments and suggests UUID item IDs, but adds little new semantics and gives no concrete collection_id value or explanation of reason beyond the schema.

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 specific action and resource are clear, and the items-kept clause distinguishes membership removal from actual item deletion. Differentiation from siblings remains implicit because none are named.

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?

The statement that items are kept implicitly guides use for detaching items rather than deleting them. It provides no explicit when/when-not guidance, prerequisites, or named alternatives such as delete_item or add_to_collection.

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