Skip to main content
Glama

Remove Posts from Collection

remove_from_collection
DestructiveIdempotent

[Act · writes · destructive] Remove one or more posts (by post_id) from a collection. Missing members are silently ignored. Free — costs 0 credits.

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>",
      "post_ids": "<post_ids>"
    },
    "name": "remove_from_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idsYespost_ids to remove (1-1000 per call)
collection_idYesTarget collection id from list_collections

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, so the safety profile is covered; the description still adds real value by disclosing that missing members are silently ignored (so no error on a no-op removal) and that the call consumes 0 credits. It does not state what happens if the collection_id itself is invalid, but that is a minor gap given the annotation coverage.

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?

Two compact sentences plus a leading categorical tag ([Act · writes · destructive]); the mutation/safety signal is front-loaded and the cost note reserves minimal space.

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 two-parameter mutation with full schema coverage and annotations carrying the destructive/idempotent profile, the description covers purpose, no-op behavior, and cost. Only the failure mode for an unknown collection is unaddressed.

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%, with post_ids documented as 1-1000 items and collection_id pointing at list_collections, so the baseline is 3. The description only echoes the post_id-by-name convention and adds no format or batching nuance 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?

States a specific verb and resource: remove one or more posts from a collection, scoped by post_id. It is unambiguous against add_to_collection, though it never names an alternative explicitly and relies on the tool name for that contrast.

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?

Usage is implied rather than stated: the description makes clear it is the removal counterpart to adding, and that it costs nothing, but gives no explicit when-to-use/when-not criteria or pointers to sibling operations such as remove_from_segment for a different resource type.

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