Skip to main content
Glama
Sign In
postman-mcp-server

postman-mcp-server

by delano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_workspace_roles

Update roles for users, groups, or teams in a Postman workspace. Supports up to 50 operations per call.

Instructions

Update workspace roles for users and groups (limited to 50 operations per call)

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": {
      "workspaceId": "<workspaceId>",
      "operations": "<operations>"
    },
    "name": "update_workspace_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationsYes
workspaceIdYesThe workspace ID
identifierTypeNoOptional SCIM identifier type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description adds one behavioral detail: a limit of 50 operations per call. However, it does not disclose authentication needs, side effects, or what happens on partial success/failure.

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?

A single sentence that efficiently conveys the core function and a key constraint. No unnecessary words or repetition.

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 description lacks information about return values, error handling, and required permissions. Given the complexity of the input schema and the absence of an output schema, the description is insufficient for an agent to fully understand the tool's behavior.

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 schema covers 67% of parameters with description. The tool description does not add meaning beyond what the schema already provides, e.g., no explanation of the identifierType field or the operation structure.

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 it updates workspace roles for users and groups, with a limit of 50 operations. It differentiates from sibling tools like get_workspace_roles. However, it omits 'teams' even though the schema includes /team paths, causing slight ambiguity.

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 guidance is provided on when to use this tool versus alternatives such as get_workspace_roles or list_workspace_roles. The description does not mention prerequisites or context for invocation.

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

Deploy Server

Other Tools