postman-mcp-server

transfer_collection_items

Copy or move requests, folders, or responses between Postman collections or folders with specified placement.

Instructions

Transfer items between collections

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": {
      "type": "<type>",
      "ids": "<ids>",
      "target": "<target>",
      "mode": "<mode>"
    },
    "name": "transfer_collection_items"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	IDs of items to transfer
`mode`	Yes	Transfer mode
`type`	Yes	Type of items to transfer
`target`	Yes	Target collection/folder information
`location`	No	Location details for placement

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits such as whether the operation is destructive, permissions required, or effects on original items. It only states 'transfer', failing to clarify that it can copy or move, and omits any behavioral implications.

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 very concise with a single sentence, containing no fluff. However, it is arguably too minimal and does not front-load critical information. Still, it earns its place by being succinct.

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?

Given the tool's complexity (5 parameters, nested objects, enums, no output schema, no annotations), the description is severely lacking. It does not explain the effect of the operation, the distinction between copy and move, or how target and location interact, making it incomplete for effective use.

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%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for parameters like type, ids, target, location, and mode.

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 the verb 'transfer' and resource 'items between collections', but it is generic and does not differentiate from other tools. However, no sibling tool performs a similar transfer operation, so it stands out. The specifics of what 'items' refers to are provided in the schema.

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, nor on prerequisites or the difference between copy and move modes. The description offers no usage context, leaving the agent uninformed about appropriate scenarios.

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

Deploy Server