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.

Input Schema

TableJSON 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.

Output Schema

TableJSON 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. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The description discloses behavioral aspects beyond the annotations: it indicates the operation is asynchronous ('Returns an embedPostId to track progress') and suggests using check_status to monitor completion. It also mentions the alternative '_and_wait' for synchronous blocking. However, it does not explicitly state that the operation is not idempotent or that it may consume credits, though annotations already imply non-idempotence.

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 moderately lengthy but each sentence is purposeful. It is structured logically: first the main purpose, then the contrast with carousel, then notes on optional defaults, and finally the workflow. No redundant or filler content is present, though it could be slightly more concise without losing critical details.

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 tool with a nested object schema and multiple optional parameters, the description is highly complete. It covers the core usage, the distinction from siblings, the asynchronous workflow, and the conditions under which parameters can be omitted. It also mentions the 'generateImages' feature and its implications (requires paid plan, consumes quota, adds latency), which is important context for the agent.

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 description adds significant semantic value beyond the schema. It clarifies that 'slide' must be a single object, not an array, and that only 'heading' is required. It explains the 'infographic' layout type and its relationship to carousel infographics, and notes that 'responseType' defaults to 'DESIGN' for faster operation. This directly resolves ambiguities present 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?

The description clearly states the tool's purpose: 'Create a single-image post (postType IMAGE) from one slide of your own content.' It explicitly distinguishes it from carousel posts and explains the key difference (single object vs array). It also mentions the return of an embedPostId for tracking, reinforcing the core function.

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?

The description provides explicit usage guidance: it contrasts with carousel usage, explains when to use this vs. the '_and_wait' variant, and mentions that parameters like templateId, brandId, and responseType can be omitted if defaults are saved. It also directs users to postnitro_check_status and postnitro_get_output for monitoring and retrieval, giving a clear workflow.

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?