Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Swagger: Create Portal Product

swagger_create_portal_product
Idempotent

Create a new portal product from scratch or copy an existing one, setting name, URL slug, and visibility.

Instructions

Create a new product for a specific portal.

Toolset: Products

Parameters:

  • portalId (string) required: Portal UUID or subdomain - unique identifier for the portal instance

  • type (string) required: Product creation type - 'new' to create from scratch or 'copy' to duplicate an existing product

  • productId (string): Source product UUID to copy from - required when type is 'copy', specifies which existing product to duplicate. Omit when type is 'new'

  • name (string) required: Product display name - will be shown to users in the portal navigation and product listings (3-40 characters)

  • slug (string) required: URL-friendly identifier for the product - must be unique within the portal, used in URLs (e.g., 'my-api' becomes /my-api). 3-22 characters, lowercase, alphanumeric with hyphens, underscores, or dots

  • description (string): Product description - explains what the API/product does, shown in product listings and cards (max 110 characters)

  • public (boolean): Whether the product is publicly visible to all portal visitors - false means only authenticated users with appropriate roles can access it

  • hidden (boolean): Whether the product is hidden from the portal landing page navigation menus - useful for internal or draft products

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProduct display name - will be shown to users in the portal navigation and product listings (3-40 characters)
slugYesURL-friendly identifier for the product - must be unique within the portal, used in URLs (e.g., 'my-api' becomes /my-api). 3-22 characters, lowercase, alphanumeric with hyphens, underscores, or dots
typeYesProduct creation type - 'new' to create from scratch or 'copy' to duplicate an existing product
hiddenNoWhether the product is hidden from the portal landing page navigation menus - useful for internal or draft products
publicNoWhether the product is publicly visible to all portal visitors - false means only authenticated users with appropriate roles can access it
portalIdYesPortal UUID or subdomain - unique identifier for the portal instance
productIdNoSource product UUID to copy from - required when type is 'copy', specifies which existing product to duplicate. Omit when type is 'new'
descriptionNoProduct description - explains what the API/product does, shown in product listings and cards (max 110 characters)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
slugNo
hiddenNo
publicNo
portalIdNo
descriptionNo
Behavior3/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds constraints (character limits, slug format) and conditional parameter behavior, but does not clarify the idempotent behavior (e.g., whether repeated calls update or fail). This gap reduces transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose, listing all parameters in a bullet-like format. It starts clearly but could be more concise by grouping related details. The structure is adequate but not optimized.

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?

Given the presence of an output schema, the description does not need to cover return values. It includes important constraints and conditional logic. However, it lacks information on authentication requirements or conflict handling, which would enhance completeness.

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 100%, so the description adds value by explaining conditional requirements (productId for 'copy'), character limits, and slug format. While much is duplicated, the added details on constraints and dependencies are beneficial.

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 title and description clearly state 'Create a new product for a specific portal.' The parameter explanations distinguish between 'new' and 'copy' creation types. Sibling tools like swagger_delete_portal_product and swagger_update_portal_product confirm this tool's unique purpose.

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?

The description provides conditional usage details (e.g., productId required when type='copy'), but does not explicitly state when to choose this tool over alternatives like updating or deleting a product. The context is clear but lacks comprehensive guidelines.

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/SmartBear/smartbear-mcp'

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