postman-mcp-server

create_collection_response

Creates a new response for a request in a collection by specifying collection ID, request ID, and response details such as name, status code, and status.

Instructions

Create a new response in a collection

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>",
      "request_id": "<request_id>",
      "response": "<response>"
    },
    "name": "create_collection_response"
  }
}

Input Schema

Name	Required	Description
`response`	Yes	Response details
`request_id`	Yes	Parent request ID
`collection_id`	Yes	Collection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided. Description only states the creation action, with no disclosure of side effects, permissions required, idempotency, or error conditions. Schema shows required params but no behavioral traits beyond creation.

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?

Single sentence, front-loaded with action, no unnecessary words. Highly concise.

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 creation tool with a nested object parameter and no output schema, the description is too brief. Missing context on success response, error conditions, and relationship to parent entities (collection, request). Sibling tools like get_collection_response might offer more detail, leaving this one incomplete.

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 baseline is 3. Description adds no extra meaning beyond what the schema already provides. Could have elaborated on the response object's valid values or constraints.

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?

Description clearly states verb and resource: 'Create a new response in a collection'. Differentiates from siblings like update_collection_response and delete_collection_response. However, lacks context on what a 'response' represents (e.g., mock response).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like create_server_response or when not to use it. No exclusions or context provided.

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

Deploy Server