Skip to main content
Glama

createCollectionResponse

Create a response for a request within a Postman collection by providing status code, headers, body, and other response details.

Instructions

Creates a request response in a collection. For a complete list of request body properties, refer to the Response entry in the Postman Collection Format documentation.

Note:

It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a response with a blank name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionIdYesThe collection's ID.
requestYesThe parent request's ID.
nameNoThe response's name. It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a response with a blank name.
descriptionNoThe response's description.
urlNoThe associated request's URL.
methodNoThe request's HTTP method.
headersNoA list of headers.
dataModeNoThe associated request body's data mode.
rawModeDataNoThe associated request body's raw mode data.
dataOptionsNoAdditional configurations and options set for the request body's various data modes.
responseCodeNoThe response's HTTP response code information.
statusNoThe response's HTTP status text.
timeNoThe time taken by the request to complete, in milliseconds.
cookiesNoThe response's cookie data.
mimeNoThe response's MIME type.
textNoThe raw text of the response body.
languageNoThe response body's language type.
rawDataTypeNoThe response's raw data type.
requestObjectNoA JSON-stringified representation of the associated request.
Behavior3/5

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

Annotations indicate mutation but not destructive. The description adds a useful behavioral note about the name defaulting to null, but does not disclose other potential side effects like authorization requirements or error conditions.

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

Conciseness4/5

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

The description is relatively concise with two sentences, no fluff. However, the first sentence is redundant with the title, and the external reference could be integrated more efficiently.

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?

Given the tool has 19 parameters, complex nested objects, and no output schema, the description is insufficient. It does not explain how parameters relate (e.g., that it creates a response under a parent request) or what the tool returns, leaving gaps for an agent.

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 parameter meanings are already well-defined. The description only adds a note about the name parameter, which repeats schema info, providing no new semantic value for other parameters.

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?

The description clearly states the tool creates a request response within a collection, using a specific verb and resource. However, it does not explicitly differentiate from the sibling tool 'createCollectionRequest' which creates a request, but the context makes it clear.

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 explicit guidance on when to use this tool vs alternatives. The description only mentions a recommendation about the name parameter but lacks context about prerequisites or exclusions.

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