Skip to main content
Glama

create_collection

Create a collection (a group of playbooks). Use when none of the existing collections from list_collections fit a new automation. Returns the collection including its id for create_playbook. name is required; description and color are optional. Slug is derived server-side. The new collection is shared with All Members.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCollection name, e.g. "Marketing" or "DevOps"
colorNoOptional hex accent color, e.g. "#6366f1"
descriptionNoOptional short description of what this collection groups

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real value beyond that by disclosing the access side effect ("shared with All Members") and the server-side slug derivation, both of which affect what the agent gets after the create. It stops short of covering duplicate-name behavior or permission requirements, which keeps it off a 5.

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?

Four short sentences: purpose, routing condition, return/id note, parameter summary, and access note. Every sentence carries information an agent would otherwise have to guess, and the purpose is front-loaded ahead of the usage rule.

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

Completeness5/5

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

For a 3-parameter creation tool with no output schema, the description covers the missing return semantics ("Returns the collection including its id"), the sharing behavior, and the routing condition. Nothing an agent needs to call this correctly is absent.

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 coverage is 100%, so the required/optional breakdown for name, description, and color is already in the schema and the description only restates it. However, "Slug is derived server-side" adds meaning the schema never conveys — it tells the agent not to look for or supply a slug field.

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+resource ("Create a collection") and immediately defines the resource as "a group of playbooks", which is not derivable from the name alone. It also distinguishes the call from the create_* siblings by naming the downstream consumer (create_playbook) and the listing sibling.

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?

"Use when none of the existing collections from list_collections fit a new automation" gives an explicit precondition and names the sibling tool to consult first. That is effectively both when-to-use and when-not-to-use, with the alternative identified rather than left 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