PostNitro

Get Post Output

postnitro_get_output

Read-onlyIdempotent

Retrieve the generated output for a completed post. Always returns the design's designId (the value to pass when scheduling — postnitro_create_scheduled_post / postnitro_generate_and_schedule) and an editorUrl deep link to open it in the editor. For PDF/PNG/MP4 output it also returns the rendered file(s) as public URLs (data, mimeType, outputType) — a single URL for PDF and MP4, one per page for PNG; for DESIGN output there is no rendered file, so those fields are omitted.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`embedPostId`	Yes	The embed post ID of a completed post

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Public URL of the rendered file — a single URL for PDF and MP4, an array of them for PNG (one per page). Omitted for responseType 'DESIGN'.
`name`	No	Design name
`status`	Yes	Job status, e.g. 'COMPLETED'
`designId`	No	Design ID — the value to pass as designId when scheduling. Absent only when it could not be resolved from the output.
`mimeType`	No	MIME type of the rendered file. Omitted for responseType 'DESIGN' (no file is rendered).
`editorUrl`	Yes	Deep link that opens the design in the PostNitro editor; null when it cannot be resolved
`outputType`	No	Rendered output type: 'pdf', 'png', or 'mp4'. Omitted for responseType 'DESIGN'.
`aspectRatio`	No	Design aspect ratio, e.g. '4:5'
`creditsUsed`	No	Credits consumed by this post
`embedPostId`	Yes	The generation-job ID
`responseType`	Yes	Output format of the post: 'PDF', 'PNG', 'DESIGN', or 'MP4' (video posts)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds concrete behavioral details: what fields are always returned, what fields are conditionally present for PDF/PNG/MP4, and that DESIGN output omits rendered file fields. This gives the agent a clear expectation of the tool's response.

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?

The description is a single, well-structured paragraph that covers all necessary aspects without redundancy. Each clause adds meaningful information (what is returned, when it applies, and the conditional output), and no irrelevant details are included.

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 the tool's simplicity (one parameter, simple output), the description is complete. It explains the purpose, the input, the output structure, and the edge case (DESIGN output). The agent has everything needed to invoke this tool correctly without ambiguity.

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?

The sole parameter embedPostId is described as 'The embed post ID of a completed post', which adds contextual meaning beyond the simple type. Since schema coverage is 100% and the description enriches the parameter's purpose, it exceeds the baseline.

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 verb 'Retrieve' and the resource 'generated output for a completed post'. It distinguishes itself from sibling tools by explicitly mentioning the always-returned designId and editorUrl, and the conditional rendered file data, making its purpose unambiguous.

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?

It specifies the condition 'for a completed post', which tells when this tool is appropriate. It also clarifies that for DESIGN output no rendered file is returned, preventing misuse. This effectively guides selection among related tools like check_status or get_scheduled_post.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PostNitro tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools are clearly separated by verb and noun (generate_carousel vs generate_image vs generate_video, import_* vs generate_*). The generic convenience names like generate_and_wait and import_and_wait are slightly ambiguous, but their descriptions and the _wait/_schedule suffixes make them distinguishable.

Naming Consistency4/5

All tools share the postnitro_ prefix and snake_case verb-first convention. A few compound names (generate_and_schedule, import_and_wait) break the strict verb_noun pattern, but the convention is otherwise consistent and predictable.

Tool Count2/5

With 35 tools, the surface exceeds the rubric's 25+ 'too many' threshold. Many entries are convenience wrappers (_wait, _and_schedule) around the same core operations and could be consolidated to reduce overload.

Completeness4/5

The domain is well covered: generation, import, output retrieval, scheduling, brands, social accounts, audio, templates, presets, and defaults. Minor gaps remain (no delete_brand, no upload/connect for audio/social accounts), but those are largely external or non-critical.

Resources

Need Help?