Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Swagger: Create Portal Product

swagger_create_portal_product
Read-onlyIdempotent

Create a new portal product with customizable name, URL slug, and visibility settings. You can create from scratch or duplicate an existing product.

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)
Behavior1/5

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

Description contradicts annotations: readOnlyHint=true but tool is a creation operation. It does not disclose behavioral traits like side effects, permissions, or idempotency beyond what is incorrectly implied by annotations.

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?

Moderately concise with a clear header and parameter list. However, the parameter descriptions are lengthy and duplicate schema, making it slightly bloated.

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

Completeness2/5

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

Lacks output schema or description of return value. For a creation tool, expected to indicate what is returned upon success. Incomplete for a tool with 8 parameters and no output info.

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 coverage is 100%, so baseline is 3. Description adds minor context (e.g., unique slug constraint) but largely repeats schema. No significant value beyond schema.

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 'Create a new product for a specific portal.' with a specific verb and resource. It distinguishes from sibling tools like update and delete by focusing on creation.

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 like updating or deleting products. The 'Toolset: Products' note is implicit but no explicit when-to-use or when-not-to-use instructions.

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