PostNitro

Generate Image Post with AI

postnitro_generate_image

Generate a single-image post (postType IMAGE) using PostNitro's AI engine. Returns an embedPostId to track progress.

The content is AI-generated from your aiGeneration prompt — you do NOT provide slides. (To supply your own image content instead, use postnitro_import_image.)

templateId, brandId, presetId, and responseType are optional if you've saved defaults via postnitro_set_defaults. Otherwise provide them here (use the list tools to find valid IDs).

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

Input Schema

TableJSON Schema

Name	Required	Description
`brandId`	No	Brand ID (optional if saved via postnitro_set_defaults)
`presetId`	No	AI preset 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
`aiGeneration`	Yes
`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?

Discloses async behavior, that a trackable embedPostId is returned, and points to status/output retrieval. It does not mention credit consumption or possible failure modes, but the annotations do not contradict the described behavior and the readOnly/destructive hints are consistent with a generation tool.

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?

Organized with purpose first, then alternative tool, then parameter guidance, then workflow. Each sentence earns its place and there is no filler or redundancy despite covering several operational 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?

Covers the full lifecycle: create, get embedPostId, monitor, retrieve, and the wait variant. Since an output schema is present, the description need not spell out return fields, and it gives enough context for correct invocation.

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 (86%), so the description adds limited new parameter-level detail. It usefully clarifies that slides are not provided for this tool, that IDs come from list tools, and that defaults can make optional fields unnecessary—reinforcing the schema without contradicting it.

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?

Opens with a specific verb and resource: 'Generate a single-image post (postType IMAGE) using PostNitro's AI engine.' It explicitly distinguishes this from postnitro_import_image and implies contrast with carousel/video siblings, so an agent knows exactly when to select it.

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?

Gives clear operational guidance: use postnitro_check_status then postnitro_get_output, or call postnitro_generate_image_and_wait for one-step. It also tells the agent to use list tools for valid IDs and explains optional defaults, leaving no ambiguity about how to proceed.

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?