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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "embedPostId": "<embedPostId>"
    },
    "name": "postnitro_get_output"
  }
}

Input Schema

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

Output 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.
`duration`	No	Video posts: how long the video runs, in seconds
`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.

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / duration

Added value: +{
+  "description": "Video posts: how long the video runs, in seconds",
+  "type": "number"
+}

First observedSep 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety story is covered. The description adds genuine behavioral context beyond that: output varies by post type (single URL for PDF/MP4, per-page URLs for PNG, fields omitted entirely for DESIGN output). It omits failure behavior when the post isn't finished yet.

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 first sentence front-loads the core purpose, then the return-shape detail follows in a logical order. It is dense with parenthetical detail but each clause (designId handoff, editorUrl, per-type file behavior) carries information the agent needs.

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?

With an output schema, annotations, and a single documented param, the description is nearly complete — it covers the workflow handoff (designId) and the conditional return shape. The only gap is what happens when the post is incomplete or the ID is invalid.

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?

Only one parameter, embedPostId, and the schema already documents it at 100% coverage. The description adds no further meaning about the ID (e.g., where it comes from), so it neither compensates nor detracts — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Retrieve the generated output for a completed post.' It also names the artifacts returned (designId, editorUrl, rendered files), which lets an agent distinguish it from get_post/get_scheduled_post. It doesn't explicitly contrast with those siblings, so it falls short of a 5.

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?

The 'completed post' precondition implies you must wait for generation before calling, and it names the downstream tools (postnitro_create_scheduled_post / postnitro_generate_and_schedule) that consume the returned designId. It never explicitly tells the agent to use a different tool when the post is not yet complete, so no exclusions are present.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?