Skip to main content
Glama

Create a collection

create_collection

Create a collection, or a sound board with kind "board". Limits are counted per kind: free accounts can have 1 collection and 1 sound board; Pro accounts can have up to 1,000 of each and can create 60 per hour. Set commercial false before adding CC BY-NC tracks; CC BY-NC tracks cannot go in a commercial collection.

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
kindNocollection (the default) or board, a collection the website plays as a grid of pads.
nameYesCollection name, 1 to 80 characters.
commercialNoWhether the collection is for commercial use. Defaults to true.

Output Schema

NameRequiredDescriptionDefault
idYes
kindYes
nameYes
itemsYes
createdYes
updatedYes
revisionYes
read_onlyYestrue when a lapsed Pro plan has made this collection view-and-export only.
commercialYes
archived_atYesWhen the collection was archived, or null.
descriptionYesOne line of plain text, or null.
credits_headingYesThe credits block heading, or null for the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the write-operation profile (readOnly false, destructive false, non-idempotent), so the description carries the burden of operational constraints and does so: per-tier account limits, a per-hour creation rate limit, and a hard content rule that CC BY-NC tracks cannot be placed in a commercial collection. These are exactly the facts an agent needs to avoid a predictable 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?

Three sentences, each doing work: purpose, quota/rate constraints, then the licensing rule. The core verb-and-resource statement is front-loaded, and nothing is repeated from the schema or annotations.

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?

Return values are covered by the output schema and all three parameters are fully documented, so the remaining burden is behavioral, which the limits and licensing rules largely satisfy. It stops short of stating what happens on limit-exceeded (error vs. silent failure) and whether names must be unique or collections default to private.

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 baseline is 3, but the description adds meaning beyond the schema: it clarifies that `kind` selects between a collection and a playable sound-board grid, and it gives a consequence for `commercial` (cannot hold CC BY-NC tracks) that the schema's "Whether the collection is for commercial use" does not convey.

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?

Opens with a specific verb and resource ("Create a collection") and immediately disambiguates the two variants it produces by naming the `kind: "board"` case as a sound board. An agent can distinguish it from update_collection, delete_collection, and list_collections 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?

Provides concrete preconditions rather than when-to-use alternatives: per-kind quotas (1 free / 1,000 Pro) and a rate cap (60 per hour), plus the instruction to set `commercial` false before adding CC BY-NC tracks. It never explicitly contrasts itself with update_collection or delete_collection, but those alternatives are unambiguous from the names.

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