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

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": {
      "slides": "<slides>"
    },
    "name": "postnitro_import_and_wait"
  }
}

Input 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.
`idempotencyKey`	No	Optional key that makes this call safe to retry. Generate a new one (e.g. a UUID) for each new action. If the call times out, fails with a network or 5xx error, or you are unsure it went through, call again with the SAME key and the same arguments: PostNitro returns the first call's result instead of creating a second post, charging credits again or scheduling a duplicate. Only a successful call is remembered, so after an error you can fix the arguments and retry with the same key; reusing a successful call's key with different arguments is rejected (422).

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'
`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.
`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).
`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.

Changed1 schema field changedNov 1, 2026

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Optional key that makes this call safe to retry. Generate a new one (e.g. a UUID) for each new action. If the call times out, fails with a network or 5xx error, or you are unsure it went through, call again with the SAME key and the same arguments: PostNitro returns the first call's result instead of creating a second post, charging credits again or scheduling a duplicate. Only a successful call is remembered, so after an error you can fix the arguments and retry with the same key; reusing a successful call's key with different arguments is rejected (422).",
+  "pattern": "^[\\x21-\\x7E]{1,200}$",
+  "type": "string"
+}

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

A4.3/5.0

Behavior4/5

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

Annotations already declare the non-read-only, non-destructive profile, and the description adds the blocking/polling nature, the 15-60s wait, and a concrete list of structural validation rules that will cause failure. It does not disclose credit consumption or what happens on timeout — the idempotency behavior lives only in the schema.

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?

Front-loads the one-line purpose and latency, then prerequisites, then numbered rules — a logical order for an agent to act on. Minor redundancy: several 'strict rules' restate the schema's own enum/description text, costing a few lines without new information.

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 present, return values need no explanation, and the description covers prerequisite ordering, defaults substitution, latency, and structural constraints. What remains thin is the relationship to the non-waiting sibling and what to do if the wait times out (the idempotency guidance is stranded in the schema).

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%, so baseline would be 3, but the description adds enforcement-level meaning absent from the field docs: slide ordering/count constraints, the columnCount<=3 ceiling, the cycle-first-column rule, and the infographic-replaces-image interaction. These are partly mirrored in the nested schema but framed here as hard rules an agent must satisfy before calling.

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?

States a specific verb+resource (imports custom slide content) plus the blocking behavior (polls until completion and returns the final output), which cleanly separates it from the async 'import_carousel' and the AI-driven 'generate_carousel' siblings. The 15-60 second latency note further pins down what kind of call this is.

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?

Gives an explicit prerequisite sequence ("Call postnitro_get_import_template FIRST") and clarifies that templateId/brandId/responseType can be omitted when defaults are saved. It stops short of naming when to prefer this over postnitro_import_carousel or postnitro_import_and_schedule, leaving that routing to be inferred from the 'and_wait' suffix.

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?