Skip to main content
Glama

putCollection

Idempotent

Replace a Postman collection's contents with a new collection body in v2.1.0 schema. Include item IDs to preserve existing items; otherwise items are recreated. Supports async update with Prefer header.

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
collectionIdYesThe collection ID must be in the form <OWNER_ID>-<UUID> (e.g. 12345-33823532ab9e41c9b6fd12d0fd459b8b).
PreferNoThe `respond-async` header to perform the update asynchronously.
collectionNo
Behavior4/5

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

Adds significant behavioral details beyond annotations: ID omission leads to removal/recreation, async returns 202, 100 MB limit, copy error conditions. Annotations only state idempotentHint true but description aligns. One minor gap: no mention of response structure for sync calls.

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 detailed but somewhat repetitive (ID note appears twice) and could be more concise. It is well-structured with bullet points but could trim redundant statements.

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

Completeness3/5

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

Covers main behaviors well but lacks output schema or description of sync response. Missing error conditions beyond the copy case. A comprehensive description would include what the endpoint returns for successful sync updates.

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?

The description adds crucial context for the collection body parameter (ID values importance, copy scenario, schema reference). This exceeds what the schema provides, especially given 67% schema coverage.

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 it replaces the contents of a collection using the Postman Collection v2.1.0 schema format. It specifies the need to include collection ID values and explains the behavior if omitted, distinguishing it from create or partial update tools.

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 guidance on when to use async mode, max size limit, and copy scenario. However, it does not explicitly compare to sibling tools like updateCollectionRequest, leaving some ambiguity about when to use this full replacement vs. partial update.

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