Skip to main content
Glama

create_document

Create a new document in a Polarion space. Requires project, space, module name, title, and type. Optionally add status, custom fields, and Markdown homepage content.

Instructions

Create a new Polarion document in a space.

module_name must be unique in the space (duplicate → HTTP 409) — check list_documents first. type/status validated — unknown ids raise ValueError with options; custom_fields keys validated against the document type schema.

home_page_content is Markdown → sanitized HTML, blocks auto-stamped with unique ids. Markdown tables get native Polarion styling; a paragraph starting 'Table:' directly after a table becomes a numbered caption widget. Post-create edits round-trip raw HTML via get_document(include_homepage_content_html=True) ↔ update_document; add work items via move_work_item_to_document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesDocument type (e.g. 'req_specification', 'generic').
titleYesHuman-readable document title.
statusNoInitial workflow status (project default if omitted).
dry_runNoPreview payload without writing; guards still query Polarion.
space_idYesSpace ID ('_default' = default space).
project_idYesPolarion project ID.
module_nameYesDocument identifier (e.g. 'MySpecV1'); unique within space_id, appears in the document URL.
auto_suspectNoFlag linked work items suspect on change.
custom_fieldsNoKeyed by Polarion field ID (copy keys from a sibling document); rich-text values as {'type':'text/html','value':...}.
home_page_contentNoMarkdown body; converted to sanitized HTML.
uses_outline_numberingNoEnable auto outline numbers (1, 1.1, ...).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
createdYes
dry_runYes
document_nameYes
payload_previewYes
Behavior5/5

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

Disclosures include uniqueness constraint, validation behavior (ValueError with options), custom_fields key validation, Markdown-to-HTML conversion with table styling and captions, and round-trip editing process. No contradiction with annotations (readOnlyHint=false, etc.).

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

Conciseness5/5

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

Efficient and well-structured: first sentence states purpose, then uniqueness constraint, validation, content specifics, and editing workflow. Every sentence adds value; no redundancy.

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

Completeness5/5

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

Given 11 parameters, high complexity, and numerous siblings, the description covers all critical aspects: uniqueness, validation, content transformation, round-trip editing, and integration with related tools. Output schema exists but return values are sufficiently handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage, but description adds significant value: module_name uniqueness, type/status validation, custom_fields key validation, home_page_content Markdown specifics and transformation details, and references to other tools for editing. Goes well beyond schema descriptions.

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 states 'Create a new Polarion document in a space' with specific resource and action. It clearly distinguishes from siblings like create_document_comments, get_document, update_document, etc.

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 explicit guidance on checking uniqueness via list_documents first, handling duplicates (HTTP 409), and validation errors. Also explains round-trip editing with get_document and update_document, but lacks explicit when-not-to-use scenarios.

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/devemberx/mcp-server-polarion'

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