postman-mcp-server

update_collection_roles

Update roles for a Postman collection by specifying users, groups, or teams and assigning VIEWER or EDITOR permissions.

Instructions

Update collection roles (requires EDITOR role)

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": {
      "collectionId": "<collectionId>",
      "operations": "<operations>"
    },
    "name": "update_collection_roles"
  }
}

Input Schema

Name	Required	Description	Default
`operations`	Yes
`collectionId`	Yes	The collection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It states a mutation (update) and a prerequisite, but fails to explain whether roles are replaced or merged, if changes are reversible, or what the response is. Important behavioral context is missing.

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 a single short sentence that gets straight to the point. No unnecessary words or filler.

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 mutates state but lacks critical context: no output schema, no description of return value, error conditions, or behavioral details like role replacement semantics. Given the complexity of the operations parameter, the description is 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 description coverage is 50%, and the schema already provides detailed descriptions for both parameters (collectionId, operations) including enums for operation types, paths, and roles. The description does not add additional meaning beyond the schema, so baseline 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 action (Update) and resource (collection roles), and includes a prerequisite (EDITOR role). This distinguishes it from sibling tools like get_collection_roles and patch_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 mentions the required role but does not provide guidance on when to use this tool vs alternatives such as patch_collection or get_collection_roles. No explicit when/when-not logic.

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

Deploy Server