postman-mcp-server

add_pan_element

Add APIs, collections, workspaces, or folders to your Private API Network by specifying type, name, and optional details.

Instructions

Add element or folder to Private API Network

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>",
      "name": "<name>"
    },
    "name": "add_pan_element"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Element/folder name
`type`	Yes	Element type
`summary`	No	Element summary
`elementId`	No	ID of API/collection/workspace to add
`description`	No	Element/folder description
`parentFolderId`	No	Parent folder ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral traits. It only states 'Add' but does not disclose side effects, such as requirements for element existence, folder hierarchy constraints, or idempotency. No information on permissions or error handling is given.

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 sentence that is front-loaded and contains no superfluous information. It achieves maximum conciseness while conveying the core purpose.

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 no output schema and no annotations, the description is too minimal to provide sufficient context for correct invocation. It does not explain return behavior, prerequisites (e.g., elementId must reference an existing item), or error cases. The tool's complexity with 6 parameters requires more context.

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 input schema has 100% description coverage for all 6 parameters, so the schema already provides adequate documentation. The description adds no additional meaning beyond the schema, earning the baseline score of 3.

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 'Add element or folder to Private API Network' clearly states the verb (Add), resource (element or folder), and location (Private API Network). It distinguishes from siblings like remove_pan_element and update_pan_element by focusing on addition. The enum values in the schema further specify the element types.

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 like add_api_collection or create_* tools. There is no mention of prerequisites, such as the need for the element to already exist when using elementId. The description lacks any when/when-not context.

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

Deploy Server