Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Swagger: Create Documentation Page

swagger_create_documentation_page
Read-onlyIdempotent

Create a documentation page in a SmartBear portal product with Markdown or HTML content. Specify portal, product, and title; returns 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, used to generate the page slug)

  • 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
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, used to generate the page slug)
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'.
Behavior1/5

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

The description claims to create a page, which is a write operation, but annotations have readOnlyHint=true, a direct contradiction. The description does not address this inconsistency or disclose other behavioral traits like permissions or side effects.

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-organized with a header, return info, and parameter list. It is somewhat lengthy but each parameter gets a brief explanation. It is not overly verbose, but could be slightly tighter.

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?

The description explains return values partially but omits exact structure or error scenarios. The annotation contradiction (readOnlyHint) undermines trust. For a create tool with 8 parameters, it is moderately complete but missing key behavioral transparency.

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?

The input schema has 100% description coverage. The description adds some context (e.g., pageTitle character count, slug generation) but largely repeats schema info. With high coverage, the description provides marginal added value.

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 a documentation page in a portal product, specifies supported content types, and indicates what is returned (page location details, draftUrl). It is distinct from sibling tools which create portals, products, or other entities.

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 explains functionality and parameters but does not explicitly state when to use this tool versus alternatives. It provides constraints (e.g., contentType and source compatibility) that guide usage but lacks explicit decision criteria or exclusions.

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