Skip to main content
Glama

Add Posts to Collection

add_to_collection
Idempotent

[Act · writes] Pin one or more posts (by post_id) into a collection you own — works on any collection type. On a 'manual' collection this is the only membership mechanism; on a 'smart' collection it adds the posts as extras alongside whatever the rule already matches (resolve_collection returns the union). Existing 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": "add_to_collection"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds real value beyond that: it explains why repeats are safe ('existing members are silently ignored'), pins down the union semantics visible through resolve_collection, and discloses cost ('Free — costs 0 credits'). It stops short of stating permission scope beyond 'collection you own'.

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 dense, front-loaded passage: the '[Act · writes]' tag signals the operation class immediately, followed by scope, collection-type behavior, and cost. No filler, though the heavy parenthetical chaining makes it slightly harder to scan than a two-sentence split would be.

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 no output schema, this covers operation class, collection-type semantics, idempotency, and cost. The notable gap is the return value — with no output schema, the agent gets no hint about whether it receives added counts or the resulting membership.

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 coverage is 100%, so both parameters are already documented with types, formats, and bounds (1-1000 items, collection id from list_collections). The description only loosely echoes this as 'by post_id' without adding format, batching, or partial-failure semantics. Baseline 3 is appropriate when the schema carries the load.

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 specific verb and resource: 'Pin one or more posts (by post_id) into a collection you own.' It goes further by scoping the operation across collection types, so an agent can tell it apart from related membership tools such as remove_from_collection or add_to_segment without opening any 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?

Explains the decision context clearly: on a 'manual' collection this is the only membership mechanism, on a 'smart' collection it adds extras alongside the rule. It does not name an explicit non-use case (e.g., removing posts, or when to prefer a segment instead), which keeps it from a 5.

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