Postman MCP Server

Create a request

createCollectionRequest

Create an API request inside a Postman collection. Specify URL, method, headers, authentication, and body to add a fully configured request.

Instructions

Creates a request in a collection. For a complete list of properties, refer to the Request 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 request with a blank name.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	The request's URL.
`auth`	No	The request's authorization settings.
`data`	No	The request body's form or urlencoded data.
`name`	No	The request'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 request with a blank name.
`events`	No	The request's pre-request and test scripts.
`folder`	No	The folder ID in which to create the request. By default, the system creates the request at the collection level.
`method`	No	The request's HTTP method.
`dataMode`	No	The request body's data mode.
`headerData`	No	The request's headers.
`dataOptions`	No	Additional options for the request body data.
`description`	No	The request's description.
`queryParams`	No	The request's query parameters.
`rawModeData`	No	The request body's raw mode data.
`collectionId`	Yes	The collection's ID.
`graphqlModeData`	No	The request body's GraphQL mode data.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.12.3Sep 16, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description adds a behavioral detail that omitting 'name' results in a blank name, which goes beyond the schema. However, it does not disclose idempotency, side effects, or what happens on error. The annotations already indicate readOnlyHint=false and destructiveHint=false, so there is no contradiction, but the behavioral context is limited to the null-name note.

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 short and front-loaded with the purpose. The note about name is concise and relevant. The external documentation link adds value without overloading the expression.

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?

The tool has no output schema, and the description does not explain what the tool returns or how the generated collection request is identified. It also does not mention that collectionId is required or the implications of folder placement, leaving an important gap for the 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% for all 15 parameters, so the schema provides the parameter meaning and the description adds no significant extra insight beyond the external documentation link. The name recommendation is repeated from the schema, offering no additional parameter semantics.

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 clear states a specific verb and resource: 'Creates a request in a collection.' It distinguishes itself from siblings like createCollection and createCollectionResponse by specifying 'request' and the container '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 the tool is for creating new requests in a collection, but it does not explicitly state when to use it vs. updateCollectionRequest or other creation tools. The note about name is a practical recommendation, but it does not provide explicit 'when to use' or '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.

Create a request

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools