Skip to main content
Glama

create_postman_collection

Create a Postman collection from a project directory by specifying a JSON file path, project name, and description. Generates the collection for API testing and documentation.

Instructions

Create a Postman collection from a directory structure. Extension of the file must be .json

Args:
    file_path: The path to the file to create the Postman collection from (string)
    name: The name of the project (string)
    description: The description of the project (string)
Returns:
    The initial Postman collection in JSON format (string)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
nameYes
descriptionYes
Behavior3/5

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

No annotations provided, so description must disclose behavior. It states it creates a collection and returns JSON, but does not clarify side effects (e.g., whether it saves to disk) 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?

Description is mostly concise with a clear title, constraint, and structured Args/Returns. However, the constraint line could be integrated more efficiently.

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?

Given no output schema and 3 required params, description covers input and return type but lacks details on behavior, error handling, and how it fits with sibling tools.

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%, so description compensates by explaining each parameter: file_path as the source, name and description as project details. This adds meaning beyond the raw schema.

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 states 'Create a Postman collection from a directory structure' with a specific verb and resource, and includes a constraint on file extension. However, it does not differentiate from sibling tools that also deal with Postman collections.

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. No prerequisites, exclusions, or context for when not to use it. The Args section only lists parameters without usage advice.

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