Skip to main content
Glama
snyk

Snyk API & Web MCP Server

Official
by snyk

probely_create_api_target_from_postman

Imports a Postman collection to create an API target for security scanning. Accepts collection URL or JSON and allows duplicate target creation.

Instructions

Create an API target from a Postman collection. Provide either postman_collection_url or postman_collectionjson.

Set allow_duplicate=True to create a target even if another target with the same URL already exists. This is useful when you want multiple targets for the same URL with different configurations (e.g., different auth methods, different test scenarios).

If target creation fails because the target is unreachable or the domain cannot be resolved, ask the user whether to retry with skip_reachability_check=True.

IMPORTANT: The response contains a top-level id (the target ID) and a nested site.id (the site ID). Always use the top-level id as the targetId parameter for all subsequent tool calls (update_target, start_scan, etc.). Do NOT use the nested site.id field for target operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
target_urlYes
postman_collection_urlNo
postman_collectionjsonNo
descNo
labelsNo
allow_duplicateNo
skip_reachability_checkNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses behavior: creation process, duplicate handling, reachability check failure, and response structure (top-level id vs nested site.id). This is comprehensive for a mutation tool.

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 well-structured with clear paragraphs and front-loaded purpose. It is somewhat lengthy but each sentence adds value. Minor redundancy could be trimmed, but overall efficient.

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

Completeness5/5

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

Given 8 parameters (2 required), no annotations, and presence of output schema, the description fully covers purpose, parameter usage, error handling, and response semantics. It equips the agent to handle edge cases like duplicates and unreachability, making it complete.

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 description coverage is 0%, but the description adds meaning for key parameters: postman_collection_url, postman_collectionjson, allow_duplicate, skip_reachability_check. However, it does not describe 'desc' or 'labels', leaving some ambiguity. Overall good coverage.

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 the tool creates an API target from a Postman collection, distinguishing it from siblings like probely_create_api_target_from_openapi and probely_create_web_target. It specifies the resource (API target) and source (Postman collection).

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use which parameters (postman_collection_url vs postman_collectionjson), when to set allow_duplicate and skip_reachability_check, and instructs the agent to ask the user on failure. Also clarifies that the top-level 'id' should be used for subsequent calls, not 'site.id'.

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/snyk/saw-mcp'

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