Skip to main content
Glama

add_postman_collection_auth

Adds or updates authentication information in a Postman collection file by specifying the auth type and parameters, supporting methods like bearer token.

Instructions

Add or update authentication information for the Postman collection

Args:
    file_path: The path to the Postman collection file (string)
    auth: The auth dictionary with type and necessary auth parameters (dict)
          Example: {
              "type": "bearer",
              "bearer": [
                  {
                      "key": "token",
                      "value": "{{token_variable}}",
                      "type": "string"
                  }
              ]
          }
Returns:
    The updated Postman collection data (dict)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
authYes
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions mutation ('add or update') and return of updated data, but lacks details on side effects, required permissions, error conditions, or idempotency.

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 follows a clear docstring format with Args and Returns. The example helps but is well-placed. No redundant sentences.

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

Completeness4/5

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

With two parameters, no output schema, and no annotations, the description covers purpose, parameters, and return value adequately. It does not address edge cases or error handling, but the tool's simplicity makes this acceptable.

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% (no descriptions), but the description explains both parameters: file_path as path and auth as dictionary with a concrete example. This adds significant meaning beyond the bare 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 clearly states the verb 'add or update' and the resource 'authentication information for the Postman collection'. Given sibling tools, this is distinct enough for an agent to identify the tool's purpose.

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, such as whether the file must exist, or when not to use it.

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