Skip to main content
Glama

Inspect Postman collection

inspect_postman_collection
Read-only

Maps a Postman collection without executing requests, letting agents see folders and items before running or modifying tests.

Instructions

Returns a lightweight map of the collection without running it, so the agent can see what exists before calling other tools.

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": {
      "collectionSource": "<collectionSource>"
    },
    "name": "inspect_postman_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNoLimit inspection to a folder
maxItemsNoMaximum number of listed items
collectionSourceYesCollection (path, https URL, or Postman UID)

Output Schema

NameRequiredDescriptionDefault
nameYes
itemsYes
foldersYes
truncatedYes
variablesYes
totalItemsYes
schemaVersionYes
collectionScriptsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds non-obvious behavioral context beyond that: the collection is not executed and the response is a 'lightweight map' rather than full content — meaningful for a tool that reaches an https URL or Postman UID.

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?

One sentence, front-loaded with the action and resource, then the non-execution constraint, then the rationale. No filler and nothing an agent must read past to find the core statement.

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 an output schema present, return shape needn't be explained, and annotations plus full schema coverage carry the rest. The remaining gap is minor: it doesn't clarify how inspection differs from validation or which sibling to call next, but nothing required for correct invocation is missing.

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?

Schema description coverage is 100%, so all three parameters (collectionSource, folder, maxItems) are documented in the schema itself. The description contributes nothing additional about formats, defaults, or the 500-item ceiling, so the baseline 3 applies.

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 gives a specific verb and resource ('Returns a lightweight map of the collection') and adds a differentiating qualifier ('without running it'), so an agent can tell it apart from execution-oriented siblings like run_newman_collection. It stops short of naming a specific sibling, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'so the agent can see what exists before calling other tools' implies a discovery-first usage pattern, which is genuinely useful sequencing guidance. However, it never states when NOT to use it (e.g., versus validate_postman_collection) and names no concrete alternative, so guidance remains implied rather than explicit.

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