Skip to main content
Glama

Create Post Collection

create_collection

[Act · writes] Create a new post collection for the authenticated user. Set type='manual' to hand-curate posts with add_to_collection, or type='smart' with a config predicate (e.g. {format:'video',min_likes:50}) to define a dynamic collection resolved on-demand by resolve_collection. 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": {
      "name": "<name>",
      "type": "<type>"
    },
    "name": "create_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUser-facing collection name
typeYes'manual' = hand-curated post list. 'smart' = dynamic predicate (requires `config`).
configNoPredicate for smart collections. Supported keys: format, min_likes, min_comments, date_after, date_before, topic_contains, author_profile_id, profile_ids (array — posts whose profile_id is in the set; use to group several tracked profiles/streams into one live collection), source_type. Required when type='smart'.
descriptionNoOptional longer description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, so the safety bar is lower. The description goes beyond them by disclosing cost (0 credits) and the key behavioral asymmetry — smart collections are predicates resolved on demand rather than materialized at creation time. It stops short of saying whether duplicate names are allowed or what happens on validation failure.

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 sentences with a leading mode tag "[Act · writes]" that front-loads the operation class. Every clause carries load: mode routing, sibling handoff, and cost. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a mutation with no output schema, yet the description never states what is returned (e.g. a collection id needed for the subsequent add_to_collection call). With 100% schema coverage and solid annotations the core call is well-specified, but the post-call handoff is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds an inline example predicate ({format:'video',min_likes:50}) that concretizes the nested config object and reiterates the conditional requirement of config for type='smart'. That is genuine meaning beyond the schema text, particularly for the nested-object case.

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?

Specific verb+resource ("Create a new post collection") with scope explicitly narrowed to the authenticated user. It immediately distinguishes the two modes the tool supports and names the sibling tools that consume each mode, so an agent can tell it apart from create_stream, create_segment, and create_campaign without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: type='manual' for hand-curated lists consumed by add_to_collection, type='smart' with a config predicate for dynamic collections consumed by resolve_collection. When-to-use for each variant and the downstream alternative are both stated, leaving nothing to inference.

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