Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Swagger: Create Documentation Page

swagger_create_documentation_page
Idempotent

Create a documentation page in a SmartBear portal product with markdown or HTML content, returning page location and draft URL for editing.

Instructions

Create a documentation page in a portal product in a single tool call. Supports markdown and html content types. Returns the page location details (productId, sectionId, slug) and a draftUrl to edit it in the portal.

Toolset: Documents

Parameters:

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

  • productId (string) required: Product UUID - unique identifier for the product

  • pageTitle (string) required: Title of the documentation page - will be displayed in navigation (3-255 characters)

  • pageSlug (string): URL slug for the documentation page. 3-255 characters, lowercase, alphanumeric with hyphens, underscores, or dots (e.g. 'my-page'). If not provided, the slug is generated from the page title.

  • pageContent (string): Content of the documentation page. Provide HTML when contentType is 'html', Markdown when contentType is 'markdown'.

  • contentType (enum): Content type of the documentation page. 'markdown' works with both 'internal' and 'external' source. 'html' only works with 'external' source — html + internal is not supported by the API and will return an error. (default: "markdown")

  • source (enum): Where the document content is managed. 'internal': editable in both the portal UI and via API. 'external': editable via API only, not in the portal UI. Constraint: 'html' content type only supports 'external' source. (default: "internal")

  • order (number): Order position of the documentation page within its parent section or item (default: 0)

  • parentId (string): Parent table of contents item ID - null for top-level pages, or ID of parent item for nested structure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoOrder position of the documentation page within its parent section or item
sourceNoWhere the document content is managed. 'internal': editable in both the portal UI and via API. 'external': editable via API only, not in the portal UI. Constraint: 'html' content type only supports 'external' source.internal
pageSlugNoURL slug for the documentation page. 3-255 characters, lowercase, alphanumeric with hyphens, underscores, or dots (e.g. 'my-page'). If not provided, the slug is generated from the page title.
parentIdNoParent table of contents item ID - null for top-level pages, or ID of parent item for nested structure
portalIdYesPortal UUID or subdomain - unique identifier for the portal
pageTitleYesTitle of the documentation page - will be displayed in navigation (3-255 characters)
productIdYesProduct UUID - unique identifier for the product
contentTypeNoContent type of the documentation page. 'markdown' works with both 'internal' and 'external' source. 'html' only works with 'external' source — html + internal is not supported by the API and will return an error.markdown
pageContentNoContent of the documentation page. Provide HTML when contentType is 'html', Markdown when contentType is 'markdown'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftUrlNo
productIdNo
sectionIdNo
sectionSlugNo
Behavior4/5

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

Annotations indicate idempotentHint: true and destructiveHint: false. The description adds context beyond annotations by explaining the returned draftUrl, the constraint that 'html + internal is not supported' and that 'external' source is editable only via API. No contradictions with annotations.

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 an intro, toolset label, and parameter list. It is front-loaded with the core purpose. The parameter list is lengthy but necessary for clarity. No redundant information.

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 9 parameters (3 required) and an output schema, the description covers creation behavior, content type/source interaction, and return values (productId, sectionId, slug, draftUrl). It lacks explicit error handling details but is sufficient for a creation tool.

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 baseline is 3. The description repeats parameter descriptions from the schema, adding minor extras like character limits (e.g., '3-255 characters') and example slugs ('my-page'). Does not significantly enhance understanding beyond the 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 documentation page in a portal product in a single tool call.' It specifies the resource (documentation page) and action (create), distinguishing it from sibling tools like swagger_create_portal or swagger_create_portal_product. Support for markdown and html content types further clarifies scope.

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?

The description implies usage by noting 'in a single tool call' and listing parameters, but does not explicitly state when to use this tool vs alternatives (e.g., swagger_update_document for updating). No when-not or exclusions are provided beyond the content type/source constraint.

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