Skip to main content
Glama
postmanlabs

Postman

Official
by postmanlabs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Create a response

createCollectionResponse

Create an HTTP response record within a Postman collection using request ID, status, headers, and body details. Specify metadata like response time and MIME type for accurate API documentation.

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
urlNoThe associated request's URL.
mimeNoThe response's MIME type.
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.
textNoThe raw text of the response body.
timeNoThe time taken by the request to complete, in milliseconds.
methodNoThe request's HTTP method.
statusNoThe response's HTTP status text.
cookiesNoThe response's cookie data.
headersNoA list of headers.
requestYesThe parent request's ID.
dataModeNoThe associated request body's data mode.
languageNoThe response body's language type.
dataOptionsNoAdditional configurations and options set for the request body's various data modes.
descriptionNoThe response's description.
rawDataTypeNoThe response's raw data type.
rawModeDataNoThe associated request body's raw mode data.
collectionIdYesThe collection's ID.
responseCodeNoThe response's HTTP response code information.
requestObjectNoA JSON-stringified representation of the associated request.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed19 schema fields changedv2.8.7
    • addedInput schema / properties / cookies
      Added value: +{
+  "description": "The response's cookie data.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / dataMode
      Added value: +{
+  "description": "The associated request body's data mode.",
+  "enum": [
+    "raw",
+    "urlencoded",
+    "formdata",
+    "binary",
+    "graphql"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / dataOptions
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "binary": {
+          "additionalProperties": {},
+          "description": "Options for the `binary` data mode.",
+          "type": "object"
+        },
+        "graphql": {
+          "additionalProperties": {},
+          "description": "Options for the `graphql` data mode.",
+          "type": "object"
+        },
+        "params": {
+          "additionalProperties": {},
+          "description": "Options for the `params` data mode.",
+          "type": "object"
+        },
+        "raw": {
+          "additionalProperties": false,
+          "description": "Options for the `raw` data mode.",
+          "properties": {
+            "language": {
+              "description": "The raw mode data's language type.",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "urlencoded": {
+          "additionalProperties": {},
+          "description": "Options for the `urlencoded` data mode.",
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Additional configurations and options set for the request body's various data modes."
+}
    • addedInput schema / properties / description
      Added value: +{
+  "description": "The response's description.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / headers
      Added value: +{
+  "description": "A list of headers.",
+  "items": {
+    "additionalProperties": false,
+    "description": "Information about the header.",
+    "properties": {
+      "description": {
+        "description": "The header's description.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "key": {
+        "description": "The header's key, such as `Content-Type` or `X-Custom-Header`.",
+        "type": "string"
+      },
+      "value": {
+        "description": "The header key's value.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "key",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / language
      Added value: +{
+  "description": "The response body's language type.",
+  "type": "string"
+}
    • addedInput schema / properties / method
      Added value: +{
+  "description": "The request's HTTP method.",
+  "enum": [
+    "GET",
+    "PUT",
+    "POST",
+    "PATCH",
+    "DELETE",
+    "COPY",
+    "HEAD",
+    "OPTIONS",
+    "LINK",
+    "UNLINK",
+    "PURGE",
+    "LOCK",
+    "UNLOCK",
+    "PROPFIND",
+    "VIEW"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / mime
      Added value: +{
+  "description": "The response's MIME type.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / rawDataType
      Added value: +{
+  "description": "The response's raw data type.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / rawModeData
      Added value: +{
+  "description": "The associated request body's raw mode data.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / request
      Added value: +{
+  "description": "The parent request's ID.",
+  "type": "string"
+}
    • removedInput schema / properties / requestId
      Removed value: -{
-  "description": "The parent request's ID.",
-  "type": "string"
-}
    • addedInput schema / properties / requestObject
      Added value: +{
+  "description": "A JSON-stringified representation of the associated request.",
+  "type": "string"
+}
    • addedInput schema / properties / responseCode
      Added value: +{
+  "additionalProperties": false,
+  "description": "The response's HTTP response code information.",
+  "properties": {
+    "code": {
+      "description": "The response's HTTP response status code.",
+      "type": "number"
+    },
+    "name": {
+      "description": "The name of the status code.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "The response's HTTP status text.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "The raw text of the response body.",
+  "type": "string"
+}
    • addedInput schema / properties / time
      Added value: +{
+  "description": "The time taken by the request to complete, in milliseconds.",
+  "type": "string"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "description": "The associated request's URL.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedInput schema / required
      Previous value: -[
-  "collectionId",
-  "requestId"
-]New value: +[
+  "collectionId",
+  "request"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations are sparse (readOnlyHint false, destructiveHint false). The description adds a useful behavioral note about the name property defaulting to null, resulting in a blank name. This is extra context beyond the annotations. It doesn't contradict any annotation and provides a specific behavioral quirk that could affect usage.

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 concise: a single purpose sentence, an external documentation link, and one note about the name property. It is front-loaded with the purpose and does not waste words. However, the note could be seen as a caveat, and the link is not inline but still provides reference. It is appropriately sized for a tool with a well-specified schema.

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 is complex with 19 parameters and nested objects, but the schema covers all parameters extensively. The description is very brief and points to external docs for full property details. It does not mention the required parameters (collectionId, request) explicitly or what the tool returns. Given the complexity, the description could be more complete, but the schema and link partially compensate. It meets a minimum viable level but lacks richer context.

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?

The input schema has 100% parameter description coverage, so the description does not need to re-explain each field. The description adds only a note about the name property, which is already present in the schema's parameter description. It does not add significant semantic value beyond what the schema provides, so a baseline score of 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 verb+resource: 'Creates a request response in a collection.' This distinguishes it from sibling tools like createCollectionRequest (creates a request) and createCollection (creates a collection). It is specific and unambiguous about what the tool does.

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 gives some context (that it creates a response in a collection) but does not explicitly state when to use this tool versus alternatives. There is no guidance on when not to use it or which sibling tools might be more appropriate. It implies usage for creating a response but lacks explicit exclusions or alternative references.

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