Skip to main content
Glama

Update a collection

update_collection
Destructive

Rename a collection, set whether it is commercial, set its description (plain text, up to 200 characters) or credits heading (up to 120 characters; the saved heading replaces the default in exported credits), or archive or unarchive it. An empty description or credits_heading clears it. A rename, commercial, description or credits heading change needs its current revision; archived alone does not and is safe to repeat. Archived collections are hidden from list_collections and search_collections unless you ask for them. A collection containing CC BY-NC tracks cannot be made commercial.

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": "update_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
archivedNotrue archives, false unarchives. Needs no revision when sent alone.
revisionNo
commercialNo
descriptionNoOne line of plain text, up to 200 characters. An empty string clears it.
collection_idYes
credits_headingNoThe heading of the credits block, up to 120 characters. An empty string goes back to the default.

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?

Beyond the annotations (destructive, non-idempotent), it discloses revision requirements per field, that archiving alone is repeatable, that empty strings clear description and credits heading, that archiving hides the collection from list/search, and the CC BY-NC commercial restriction. This is meaningful behavioral context an agent cannot get from the annotations alone, and nothing contradicts them.

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?

Front-loaded with the operations, then constraints, with zero filler. The opening sentence is dense, bundling four operations plus length limits, but every sentence carries information rather than restating the title.

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?

For a 7-parameter destructive mutation with an output schema, the description covers the risk areas: revision coupling, clearing semantics, archive visibility and the commercial restriction. The one gap is not pointing at how to fetch the current revision (presumably get_collection), which the agent must discover itself.

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

Parameters5/5

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

Schema coverage is only 43%, but the description compensates: it explains the credit-heading semantics (replaces the default in exported credits) and the clearing behavior of empty strings, and it ties revision to specific field changes. That goes well past what the schema 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?

The description names the resource and enumerates the exact operations: rename, set commercial, set description or credits heading, archive/unarchive. This clearly separates it from create_collection, delete_collection and update_collection_item without the agent needing to open 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?

It gives concrete conditions: a rename/commercial/description/credits change needs the current revision, while archived sent alone does not and is safe to repeat. It also warns that archived collections are hidden from list_collections and search_collections unless requested, though it never says where to obtain the revision or when to prefer a sibling tool for other edits.

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