Skip to main content
Glama

Resolve Post Collection

resolve_collection
Read-onlyIdempotent

[Read · free] Resolve a post collection into a concrete list of post_ids. For manual / auto_stream collections, returns stored members. For smart collections, evaluates the collection's config predicate against the user's posts and returns matches. 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>"
    },
    "name": "resolve_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax post_ids to return (default 1000)
collection_idYesCollection id (from list_collections / create_collection)

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered; the description still adds real behavior: smart collections evaluate a stored `config` predicate against the user's posts while manual/auto_stream collections return stored members. The zero-credit cost statement is useful but partially duplicates the '[Read · free]' prefix, and it says nothing about result ordering or truncation when the cap is hit.

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?

Three short sentences, front-loaded with the verb and the output, with no filler prose. The only waste is the redundant cost signal — '[Read · free]' at the front and 'Free — costs 0 credits' at the end say the same thing.

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?

With no output schema, the description correctly specifies the return value as post_ids, and it explains the two resolution modes, which is the main complexity here. Minor gaps remain around ordering, deduplication, and whether truncation at `limit` is surfaced.

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 both `collection_id` and `limit` (default 1000, max 5000) documented inline, so the baseline is 3. The description mentions the returned post_ids but adds no syntax or constraint detail for `limit` beyond what the schema already states.

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 (resolve a post collection) plus the concrete output artifact (a list of post_ids), and further splits behavior by collection type (manual/auto_stream vs smart). An agent can distinguish this from mutation siblings like add_to_collection purely from the description.

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?

Gives clear context for when the tool applies and explains that the resolution semantics differ by collection type, which is the main thing an agent needs to predict the result. It does not, however, name an alternative or exclusion (e.g., when to prefer resolve_segment over this), so it stops short of full when/when-not routing.

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