PostNitro

Import Carousel and Wait for Output

postnitro_import_and_wait

Convenience tool: imports custom slide content, polls until completion, and returns the final output. May take 15-60 seconds.

IMPORTANT: Call postnitro_get_import_template FIRST to see the exact slide structure and rules.

templateId, brandId, and responseType are optional if you've saved defaults via postnitro_set_defaults.

Strict rules:

First slide MUST be type "starting_slide" (exactly 1)
Middle slides MUST be type "body_slide" (at least 1)
Last slide MUST be type "ending_slide" (exactly 1)
Infographic columnCount must not exceed 3
When columnDisplay is "cycle", data in FIRST column only
layoutType "infographic" replaces the image field

Input Schema

TableJSON Schema

Name	Required	Description
`slides`	Yes	Array of slides
`brandId`	No	Brand ID (optional if saved via postnitro_set_defaults)
`templateId`	No	Template ID (optional if saved via postnitro_set_defaults)
`requestorId`	No	Optional custom tracking ID
`responseType`	No	Output format. 'DESIGN' (default) creates the design with no rendered file — fastest, and enough for scheduling/editing. Use 'PDF' or 'PNG' when you need a rendered file back. Optional if saved via postnitro_set_defaults.
`generateImages`	No	Optional AI image generation — include this object to enable it, omit it for no images. When included, `context` is required and you (the agent) must author it from the post. Best-effort: the post still COMPLETES if images fail or aren't permitted (free plan / exhausted AI-image quota); check the GENERATE_IMAGES step via postnitro_check_status. Requires a paid plan, consumes the org's AI-image quota (separate from post credits), and adds latency.

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'
`success`	Yes	True when the post finished processing
`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).
`warnings`	No	Non-fatal issues worth surfacing to the user (e.g. AI image generation did not complete)
`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)
`usedDefaults`	Yes	The values actually applied — explicit arguments, saved defaults, or an auto-selected sole candidate

Schema Changelog

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

First observedSep 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Description discloses important behavior beyond annotations: polling until completion, 15-60 second latency, optional defaults, strict slide rules, and detailed best-effort behavior of image generation including quota consumption and failure handling. No contradictions 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?

The description is long but well-organized with a summary, an IMPORTANT prerequisite callout, and numbered strict rules. It front-loads the core purpose and then provides necessary details for a complex tool.

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 complexity, the description covers purpose, prerequisites, parameter behavior, polling, latency, and failure handling. Since an output schema exists, not detailing return values is acceptable, and the description is otherwise complete enough for correct use.

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 already high, but the description adds meaningful usage context around slide ordering, layout constraints, and the generateImages context requirement. This supplements the schema descriptions without redundancy issues.

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?

Description states exactly what the tool does: imports custom slide content, polls until completion, and returns the final output. It also distinguishes itself as a convenience wrapper with a wait-and-return behavior, separating it from sibling import tools.

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 clear guidance on prerequisites (call postnitro_get_import_template first) and optional parameters if defaults are saved. It also specifies strict structural rules for slides. It does not explicitly enumerate alternatives like postnitro_import_carousel, but the wait-for-output behavior is clearly implied.

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?