Skip to main content
Glama

Create collection

create_collection
Idempotent

Creates a collection with optional published, visible Library content.

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

Input Schema

NameRequiredDescriptionDefault
titleYes
contentNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety and idempotency profile is covered structurally. The description adds only an opaque note about 'published, visible Library content' and says nothing about permissions, what 'visible' means, or what happens when content items fail validation.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity reflects underspecification rather than tight scoping.

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

Completeness2/5

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

This is a mutating creation tool with a three-parameter schema at 0% description coverage and no output schema. The description should at minimum clarify required fields, idempotency behavior, and content-source constraints, none of which it does.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters. The description gestures at the content array but never explains that title is required, what the idempotency_key governs (despite idempotentHint=true), or what the content_type enum values mean — so it fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource ('Creates a collection') is clear, but the modifier 'with optional published, visible Library content' is ambiguous and does not clearly map to any schema field. It also gives no signal distinguishing it from siblings like create_collection_section or add_collection_content.

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

Usage Guidelines2/5

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

There is no guidance on when to create a collection versus adding content later via add_collection_content, nor any prerequisites such as whether referenced Library content must already be published/visible. The agent must infer all usage context.

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