Skip to main content
Glama

updateCollectionRequest

Idempotent

Update specific properties of a request in a Postman collection without changing its folder. Modify name, method, URL, headers, query params, body, auth, or events.

Instructions

Updates a request in a collection. For a complete list of properties, refer to the Request entry in the Postman Collection Format documentation.

Note:

  • You must pass a collection ID (`12ece9e1-2abf-4edc-8e34-de66e74114d2`), not a collection(`12345678-12ece9e1-2abf-4edc-8e34-de66e74114d2`), in this endpoint.

  • This endpoint does not support changing the folder of a request.

  • This endpoint acts like a PATCH method. It only updates the values that you pass in the request body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestIdYesThe request's ID.
collectionIdYesThe collection's ID.
nameNoThe request's name.
descriptionNoThe request's description.
methodNoThe request's HTTP method.
urlNoThe request's URL.
headerDataNoThe request's headers.
queryParamsNoThe request's query parameters.
dataModeNoThe request body's data mode.
dataNoThe request body's form data.
rawModeDataNoThe request body's raw mode data.
graphqlModeDataNoThe request body's GraphQL mode data.
dataOptionsNoAdditional configurations and options set for the request body's various data modes.
authNoThe request's authentication information.
eventsNoA list of scripts configured to run when specific events occur.
Behavior4/5

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

Annotations already provide idempotentHint=true. The description adds that it acts like a PATCH method and does not support changing the folder, which goes beyond annotations. 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?

The description is concise with three bullet points and no redundant information. Every sentence provides unique value, making it easy for an AI agent to parse quickly.

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?

Given the complexity (15 parameters) and no output schema, the description covers key behavioral aspects (PATCH, ID format, folder restriction). The schema already describes all parameters in detail, so the description supplements well.

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. The description adds a specific note about the collectionId format ('you must pass a collection ID, not a collection'), which provides additional meaning beyond the schema's description.

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 tool updates a request in a collection, specifying the verb 'updates' and resource 'request in a collection'. It distinguishes from sibling tools like createCollectionRequest (creates) and putCollection (updates 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 provides three notes (ID format, no folder change, PATCH behavior) but does not explicitly state when to use this tool vs alternatives. The notes offer context but no direct comparison with sibling tools.

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