Skip to main content
Glama

get_document

Read-only

Retrieve a document's metadata, including title, type, status, and custom fields. Optionally get raw HTML content for lossless round-trip editing.

Instructions

Get a document's metadata (and optionally its raw body source).

Returns title, type, status, and custom fields. With include_homepage_content_html=True the content_html field carries homePageContent as raw Polarion HTML — the exact shape that round-trips through update_document(home_page_content_html=...) losslessly (no Markdown conversion, no sanitization).

homePageContent is the inline prose only — heading text and embedded work-item bodies live in separate work items. For end-to-end reading use read_document; for structural metadata use read_document_parts. Only feed content_html back to update_document when the read flag was True (a False read blanks the field, and the empty string is rejected at the write side).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
space_idYesSpace ID containing the document (e.g. '_default').
document_nameYesDocument name within the space (spaces handled automatically).
include_homepage_content_htmlNoWhen True, fill ``content_html`` with raw HTML for round-trip editing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDocument title.
typeNoDocument type (e.g. 'req_specification').
statusNoDocument workflow status (e.g. 'draft', 'approved').
content_htmlNoRaw Polarion HTML body; empty unless the read flag was True.
custom_fieldsNoProject-defined custom fields keyed by field ID.
Behavior5/5

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

Annotations set readOnlyHint=true, and description confirms read-only behavior. Adds key context: 'content_html' carries raw Polarion HTML for lossless round-tripping, and 'homePageContent' is inline prose only. No contradiction 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?

Well-structured with purpose first, then flag explanation, sibling differentiation, and usage warning. Every sentence adds value, though slightly verbose in explaining round-trip details. Still clear and efficient.

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?

With an output schema present, description need not detail return values. Covers purpose, parameter semantics, behavioral traits (HTML shape, round-trip constraints), and usage boundaries relative to siblings. Fully addresses agent's needs for correct invocation.

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%, but description adds meaning beyond schema: explains round-trip relationship between 'include_homepage_content_html' and 'content_html', and clarifies that 'document_name' handles spaces automatically. This extra context justifies a 4.

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?

Starts with clear verb+resource: 'Get a document's metadata (and optionally its raw body source).' Explicitly distinguishes from siblings 'read_document' and 'read_document_parts' by stating their use cases, ensuring the agent selects this tool for metadata and round-trip HTML retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use: metadata retrieval with optional raw HTML. Excludes end-to-end reading and structural metadata by directing to siblings. Includes critical warning about feeding 'content_html' back only when read flag was True, preventing misuse.

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