postman-mcp-server

update_collection_response

Update specific response details in a Postman collection by providing only the fields to change, like name, status code, or status text.

Instructions

Update a response in a collection. Acts like PATCH, only updates provided values.

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>",
      "response_id": "<response_id>",
      "response": "<response>"
    },
    "name": "update_collection_response"
  }
}

Input Schema

Name	Required	Description
`response`	Yes	Response details to update
`response_id`	Yes	Response ID
`collection_id`	Yes	Collection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations exist, so description carries full burden. Discloses PATCH semantic (partial update), which is key behavioral info not in schema. No contradictions.

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?

Two sentences, no fluff. Front-loaded with verb and resource. Every sentence adds value.

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 patch tool with 3 required params (collection_id, response_id, response) and no output schema, the description is concise yet covers the core behavior. Could mention that omitted fields remain unchanged, but overall adequate.

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 100%, so baseline is 3. Description adds value by clarifying that parameters are partial updates ('only updates provided values'), which is beyond the schema's field 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?

Clearly states verb 'Update', resource 'response in a collection', and adds behavior 'Acts like PATCH, only updates provided values'. Distinct from siblings like create_collection_response and delete_collection_response.

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 explicit guidance on PATCH-like behavior (only updates provided values). Understandably implies when to use (partial update) but does not explicitly list alternatives or when-not-to-use.

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

Deploy Server