Skip to main content
Glama

add_postman_collection_folder

Add a folder to a Postman collection by specifying the file path and folder name, with optional items to include.

Instructions

Add a folder to the Postman collection

Args:
    file_path: The path to the Postman collection file (string)
    folder_name: The name of the folder (string)
    items: Optional list of item dictionaries to add to the folder (list of dicts)
Returns:
    The updated Postman collection data (dict)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
folder_nameYes
itemsNo
Behavior2/5

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

No annotations provided, so description must disclose side effects. It does not state whether the action modifies the file in-place or if the updated data is returned, nor any prerequisites or error conditions.

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 relatively concise with a clear Args structure. No superfluous information, though the Returns line could be integrated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers basic functionality and parameter explanations. However, missing details like file existence requirements, error handling, and the expected format of item dictionaries reduce completeness for a tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description's Args section explains each parameter's purpose (e.g., file_path is path to the collection file, items is optional list of item dicts), adding meaning beyond the schema's type and title.

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 'Add a folder to the Postman collection' with a specific verb and resource. It distinguishes from siblings like add_item_to_folder and add_postman_collection_item by focusing on folder creation.

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. With multiple sibling tools for modifying collections, the description lacks context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marioToribi0/code2postman-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server