Skip to main content
Glama
snyk

Snyk API & Web MCP Server

Official
by snyk

probely_create_api_target_from_openapi

Create an API target by providing an OpenAPI/Swagger schema via URL or JSON. Set allow_duplicate to enable multiple targets for the same URL with different configurations.

Instructions

Create an API target from an OpenAPI/Swagger schema. Provide either openapi_schema_url or openapi_schemajson. When the user provides openapi_schema_url, do not fetch the openapi_schemajson from that url.

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
openapi_schema_urlNo
openapi_schemajsonNo
descNo
labelsNo
allow_duplicateNo
skip_reachability_checkNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Discloses behavioral details such as the need to use top-level 'id' instead of 'site.id', and the option to retry with skip_reachability_check. With no annotations, the description has gaps: no mention of authorization, rate limits, or destructive nature beyond creation.

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 well-structured with clear sections and front-loaded purpose. The IMPORTANT note is necessary but slightly verbose. Overall efficient.

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?

Covers critical aspects like input methods, duplicate handling, and response ID usage. However, lacks explanation for some parameters (desc, labels) and does not fully detail output schema despite its existence. Adequate but with clear gaps.

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?

Explains key parameters (openapi_schema_url, openapi_schemajson, allow_duplicate, skip_reachability_check) but does not cover desc or labels. Since schema description coverage is 0%, the description partially compensates but leaves gaps.

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?

Description clearly states 'Create an API target from an OpenAPI/Swagger schema' with specific verb and resource. Distinguishes from sibling tools like probely_create_web_target and probely_create_api_target_from_postman.

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

Usage Guidelines4/5

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

Provides clear context on when to use parameters like allow_duplicate and skip_reachability_check, and how to handle failures. However, does not explicitly contrast with sibling tools or state when not to use this tool.

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