PostNitro

Import Single Image Post

postnitro_import_image

Create a single-image post (postType IMAGE) from one slide of your own content. Returns an embedPostId to track progress.

Unlike a carousel, an image post is ONE slide — pass slide as a single object, NOT an array, with no slide type. Only heading is required. An infographic layout IS supported: set layoutType 'infographic' + layoutConfig on the slide (same shape as carousel infographics).

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

Use postnitro_check_status to monitor, then postnitro_get_output to retrieve. Or use postnitro_import_image_and_wait for one step.

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": {
      "slide": "<slide>"
    },
    "name": "postnitro_import_image"
  }
}

Input Schema

Name	Required	Description
`slide`	Yes	The single image slide (one object, not an array). Only 'heading' is required.
`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
`status`	Yes	Initial job status ('PENDING')
`message`	No	Message returned by the PostNitro API
`success`	Yes	True when the job was accepted
`nextStep`	Yes	The suggested follow-up call
`warnings`	No	Non-fatal issues worth surfacing to the user (e.g. AI image generation did not complete)
`embedPostId`	Yes	Generation-job ID — pass to postnitro_check_status, then postnitro_get_output
`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"
+}

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior3/5

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

The description usefully supplements the annotations: it discloses that templateId/brandId/responseType fall back to saved defaults, that generateImages is best-effort and can still complete on failure, and that it requires a paid plan and consumes quota. However, it never explains the async model directly (it only implies it via 'embedPostId to track progress'), leaving the agent to infer that this returns a job rather than a finished post. Given the annotations already cover the mutation/idempotency safety profile, a 3 is appropriate.

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?

Front-loaded with the core action, then object shape, then defaults, then the follow-up workflow. Every sentence maps to a real decision the agent must make and none is wasted repetition of the name.

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?

For a mutation tool with nested infographic config and an existing output schema, the description covers the remaining gaps an agent would trip on: array-vs-object input shape, defaults handling, best-effort image generation, and the async retrieval path. Return values needn't be spelled out because the output schema exists.

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 the baseline is 3; the description earns above that by clarifying the shape contract that the schema alone makes ambiguous ('single object, NOT an array, with no slide type') and by noting that an infographic layout, though nested in the slide, is a supported variant with the same config shape as carousel infographics. It stops short of explaining per-field meanings already in the schema.

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 and resource ('Create a single-image post (postType IMAGE)') and immediately distinguishes itself from the carousel sibling ('Unlike a carousel, an image post is ONE slide — pass slide as a single object, NOT an array'). An agent can select this over postnitro_import_carousel without opening either schema.

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?

Explicit routing: use postnitro_check_status to monitor then postnitro_get_output to retrieve, or use postnitro_import_image_and_wait for a one-step flow. It also names the alternative (carousel) and the condition that separates the two (single slide vs array), leaving nothing to inference.

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?