postman-mcp-server

update_collection

Replace an existing Postman collection with a new collection in v2.1 format. Provide the collection ID and full collection details.

Instructions

Update an existing collection. Full collection replacement with maximum size of 20 MB.

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

Input Schema

Name	Required	Description	Default
`collection`	Yes	Collection details in Postman Collection Format v2.1
`collection_id`	Yes	Collection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the tool performs a full replacement and a 20 MB size limit, but lacks details on side effects (e.g., overwrites entire collection), authorization needs, or rate limits. Some transparency, but insufficient for a mutation tool.

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?

The description is a single sentence, directly front-loading the action and key constraint. No wasted words; every part contributes meaning.

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?

The tool has 2 required parameters and no output schema. The description covers purpose and size constraint but does not specify return values, error conditions, or the expected format of the request body beyond the schema. Adequate but could be more complete given the nested object parameter.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents both parameters. The description adds context ('full collection replacement, 20 MB limit') but does not add syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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 the action ('Update'), the resource ('existing collection'), and key constraints ('Full collection replacement, maximum size 20 MB'). It effectively distinguishes from sibling tools like 'patch_collection' (partial update) and 'create_collection'.

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 implies usage for updating a collection and notes it's a full replacement, but does not explicitly state when to use this tool vs alternatives like 'patch_collection' or mention prerequisites (e.g., collection must exist). Lacks clear when-not-to-use guidance.

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

Deploy Server