postman-mcp-server

fork_collection

Copy a collection to another workspace, assigning a label for identification.

Instructions

Fork a collection to a workspace

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": {
      "collection_id": "<collection_id>",
      "workspace": "<workspace>",
      "label": "<label>"
    },
    "name": "fork_collection"
  }
}

Input Schema

Name	Required	Description
`label`	Yes	Label for the forked collection
`workspace`	Yes	Destination workspace ID
`collection_id`	Yes	Collection ID to fork

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 6, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations provided; description only says 'Fork' without disclosing whether the fork is independent, if changes sync, or side effects (e.g., permissions, rate limits). Minimal behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but lacks detail. For a required 3-parameter tool, it is functional but at the edge of underspecification.

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?

Missing details on return values (no output schema), asynchronous nature, or confirmation. Incomplete for a mutation tool without annotations.

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 covers all three parameters with clear descriptions. The description adds no extra meaning beyond 'fork to workspace', which is already captured by the name and schema.

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 'Fork a collection to a workspace' clearly states the action (fork) and the resource (collection) with destination, distinguishing it from sibling tools like fork_environment and other collection operations.

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 on when to use this tool versus alternatives (e.g., clone, copy, or create). Missing prerequisites or contextual cues for decision-making.

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

Deploy Server