Skip to main content
Glama

Replace a collection's data

putCollection
Idempotent

Replaces the contents of a Postman collection using the v2.1.0 schema. Preserve items by including their IDs; omitting IDs removes and recreates items.

Instructions

Replaces the contents of a collection using the Postman Collection v2.1.0 schema format. Include the collection's ID values in the request body. If you do not, the endpoint removes the existing items and creates new items.

Note:

  • The maximum collection size this endpoint accepts cannot exceed 100 MB.

  • Use the GET `/collection-updates-tasks/{taskId}` endpoint to get the collection's update status when performing an asynchronous update.

  • If you don't include the collection items' ID values from the request body, the endpoint removes the existing items and recreates the items with new ID values.

  • To copy another collection's contents to the given collection, remove all ID values before you pass it in this endpoint. If you do not, this endpoint returns an error. These values include the `id`, `uid`, and `postman_id` values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
PreferNoThe `respond-async` header to perform the update asynchronously.
collectionNo
collectionIdYesThe collection ID must be in the form <OWNER_ID>-<UUID> (e.g. 12345-33823532ab9e41c9b6fd12d0fd459b8b).
Behavior5/5

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

Even though annotations mark destructiveHint: false, the description accurately discloses potentially destructive behavior (removing existing items if IDs not included). It also explains async behavior (returns 202), the 100 MB size limit, and error conditions when copying collections with IDs – all beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with a clear main sentence, bullets, and notes, but contains redundancy (the same warning about removing items without IDs appears twice). It is somewhat long given the amount of information, but not excessively wordy.

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 complex tool with a large schema and no output schema, the description covers key behavioral aspects: format link, async update endpoint, protocol behavior link, size limit, and copy error conditions. It does not describe sync response format, but that's minor given the complexity.

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 high (67% of top-level parameters have descriptions, and the collection object itself is heavily documented). The description adds critical guidance about including ID values in the request body and the Prefer header for async, which goes beyond schema descriptions.

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 clearly states 'Replaces the contents of a collection' – a specific verb+resource. It also specifies the format (Postman Collection v2.1.0 schema) and distinguishes from siblings like 'createCollection' or 'duplicateCollection' by focusing on replacement of existing data.

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 description explains behavior (e.g., removing items if IDs not included, async usage via Prefer header) but does not explicitly state when to use this tool versus alternatives. It implies full-replacement use case but lacks a clear 'when not to use' or comparison with updateCollectionRequest or createCollection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/postmanlabs/postman-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server