Skip to main content
Glama

Update collection

update_collection
DestructiveIdempotent

Changes collection title, description, or internal name after checking its revision.

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>",
      "collection_id": "<collection_id>",
      "expected_revision": "<expected_revision>"
    },
    "name": "update_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
descriptionNo
collection_idYes
internal_nameNo
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context by flagging an optimistic-concurrency revision check and by implicitly scoping mutation to three metadata fields. It omits what happens on a revision mismatch, permission requirements, and whether unlisted fields are preserved, which are the gaps that matter for a destructive mutation.

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?

A single sentence with no filler: the action, the mutable fields, and the precondition are all front-loaded. Nothing can be cut without losing information.

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?

For a destructive, six-parameter mutation with zero schema description coverage and no output schema, the description is thin. It never explains the idempotency contract, how expected_revision is obtained or what a conflict looks like, or what the tool returns, so an agent would likely call it with guesswork.

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%, so the description must carry the burden, and it explains only three of six parameters (title, description, internal_name). 'collection_id', 'expected_revision' (only obliquely hinted at via 'checking its revision'), and especially 'idempotency_key' are given no semantic meaning anywhere, leaving an agent to guess at the identity and retry contract.

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

Purpose4/5

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

States a specific verb-plus-resource ('Changes collection') and enumerates the mutable fields (title, description, internal name), so an agent can tell this is a metadata-update tool rather than a create/get tool. It does not name or contrast itself with siblings like create_collection or update_library_content, which keeps it just short of a 5.

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

Usage Guidelines3/5

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

The phrase 'after checking its revision' implies a precondition (fetch current revision, then update) but does not state when to prefer this tool over create_collection, update_library_content, or add_collection_content. Usage is inferable rather than instructed, and there are no explicit exclusions or failure-path guidance.

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