Skip to main content
Glama

add_postman_collection_item

Add a new API request item to an existing Postman collection file. Specify the collection path and item details like name, method, and URL.

Instructions

Add an item to the Postman collection

Args:
    file_path: The path to the Postman collection file (string)
    item: The item dictionary to add (dict containing at least 'name' and 'request' keys)
          Example: {
              "name": "Get User",
              "request": {
                  "method": "GET",
                  "url": "https://api.example.com/users/1"
              }
          }
Returns:
    The updated Postman collection data (dict)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
itemYes
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions returning updated collection data but does not state if the file is modified in-place, permissions needed, or side effects. For a mutation tool, this is insufficient.

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 first sentence states the purpose immediately. The docstring format (Args/Returns) is clear, though slightly verbose. Every sentence adds value, and the example is helpful. Could be more concise but still well-structured.

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 annotations or output schema, the description explains inputs with an example and mentions return type. However, it lacks details on file existence assumptions, error handling, or whether the tool can create a collection from scratch. It is adequate but not fully comprehensive.

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 the description compensates with a detailed example and explanation for the 'item' parameter (dict with at least 'name' and 'request' keys). This adds significant meaning beyond the schema which only specifies it as an object.

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 an item to the Postman collection', with a specific verb ('add'), resource ('Postman collection'), and what it adds ('item'). It distinguishes from siblings like add_postman_collection_folder which add folders.

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. There is no mention of prerequisites (e.g., collection file must exist) or when to use add_item_to_folder or other siblings.

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