Skip to main content
Glama

Import Video Post

postnitro_import_video

Create a video post (postType VIDEO) from your own scene content. Returns an embedPostId to track progress.

Scenes use the SAME slide array as a carousel: exactly 1 starting_slide, at least 1 body_slide, exactly 1 ending_slide — each slide becomes a scene. Infographic layouts work as they do on carousel slides.

Output: 'DESIGN' (default) creates the design without rendering; 'MP4' renders the video file.

Motion: the video is animated without asking, as its template is, or in the clean style, and runs as long as that takes (at most 2:00). videoSettings.motionStyle picks a style, built-in or saved; videoSettings.sequenceId puts a saved sequence on every slide. Find saved ones with postnitro_list_motion_styles and postnitro_list_motion_sequences.

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

Input Schema

NameRequiredDescriptionDefault
slidesYesThe scenes, as an array of 3+ typed slides (exactly 1 starting_slide first, 1+ body_slide, exactly 1 ending_slide last).
brandIdNoBrand ID (optional if saved via postnitro_set_defaults)
templateIdNoTemplate ID (optional if saved via postnitro_set_defaults)
requestorIdNoOptional custom tracking ID
responseTypeNoOutput format for a video. 'DESIGN' (default) creates the design without rendering — fastest, and enough for scheduling or finishing in the editor. 'MP4' renders the video file. A video cannot be rendered as PDF or PNG.
videoSettingsNoA video's motion, music and voiceover, all optional: without it the video is still animated. It runs as long as its motion and narration take, up to 2:00. When it's later scheduled as a reel, the API reuses its music.
generateImagesNoOptional 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.
idempotencyKeyNoOptional 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

NameRequiredDescriptionDefault
statusYesInitial job status ('PENDING')
messageNoMessage returned by the PostNitro API
successYesTrue when the job was accepted
nextStepYesThe suggested follow-up call
warningsNoNon-fatal issues worth surfacing to the user (e.g. AI image generation did not complete)
embedPostIdYesGeneration-job ID — pass to postnitro_check_status, then postnitro_get_output
usedDefaultsYesThe values actually applied — explicit arguments, saved defaults, or an auto-selected sole candidate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +}
  2. Changed10 schema fields changed
    • changedInput schema / properties / responseType / description
      Previous value: -"Output format for a video. 'DESIGN' (default) creates the design without rendering — fastest, and enough for scheduling or finishing in the editor. 'MP4' renders the video file and requires videoSettings. A video cannot be rendered as PDF or PNG."New value: +"Output format for a video. 'DESIGN' (default) creates the design without rendering — fastest, and enough for scheduling or finishing in the editor. 'MP4' renders the video file. A video cannot be rendered as PDF or PNG."
    • changedInput schema / properties / videoSettings / description
      Previous value: -"Video render settings. REQUIRED when responseType is 'MP4' (a render needs a duration); optional for 'DESIGN'. When this video is later scheduled as a reel, the API reuses these settings automatically."New value: +"A video's motion, music and voiceover, all optional: without it the video is still animated. It runs as long as its motion and narration take, up to 2:00. When it's later scheduled as a reel, the API reuses its music."
    • changedInput schema / properties / videoSettings / properties / audioId / description
      Previous value: -"Media ID of an audio track to lay over the video — an ID, NOT a URL. Get it from postnitro_list_audio; the file must already exist in this workspace, and the API rejects a URL or a non-audio ID. Omit for a silent video."New value: +"The older name of backgroundMusicId, still taken. Give one or the other, not both."
    • addedInput schema / properties / videoSettings / properties / backgroundMusicId
      Added value: +{
      +  "description": "The video's background music: a media id from postnitro_list_audio, an audio file in this workspace. Not a URL.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / videoSettings / properties / backgroundMusicVolume
      Added value: +{
      +  "description": "The music's volume, 0 to 100 (default 100). It's lowered to 30% while narration plays. Needs backgroundMusicId on a new video; on an edit it sets the video's own track.",
      +  "maximum": 100,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / videoSettings / properties / motionStyle
      Added value: +{
      +  "description": "How every slide moves: a built-in style (none, minimal, clean, slideshow, editorial, cinematic, luxe, story, typewriter, snap, bold, playful, kinetic, glitch) or a saved style's id from postnitro_list_motion_styles. Omit for the template's motion, or clean.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / videoSettings / properties / sequenceId
      Added value: +{
      +  "description": "A saved sequence's id from postnitro_list_motion_sequences: its animations on every slide, over the style.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / properties / videoSettings / properties / videoDuration
      Removed value: -{
      -  "description": "Length of the rendered video in seconds — at least 5 and under 60.",
      -  "exclusiveMaximum": 60,
      -  "minimum": 5,
      -  "type": "number"
      -}
    • addedInput schema / properties / videoSettings / properties / voiceover
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "captions": {
      +          "description": "Show the narration's words as captions (default true).",
      +          "type": "boolean"
      +        },
      +        "tone": {
      +          "description": "How it sounds: upbeat (default), calm, professional, storyteller, or your own words, up to 80 characters (\"Hype and punchy\").",
      +          "maxLength": 80,
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "voice": {
      +          "description": "The narrator's voice (default coral).",
      +          "enum": [
      +            "alloy",
      +            "ash",
      +            "ballad",
      +            "coral",
      +            "echo",
      +            "fable",
      +            "nova",
      +            "onyx",
      +            "sage",
      +            "shimmer",
      +            "verse"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "const": false,
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "An AI voiceover: the AI writes a line for every slide and records it in the voice and tone; no script is taken. {} for the defaults. Costs the plan's AI tokens (the script's, and 5,000 a minute of audio), not API credits; best-effort, so with the tokens used up the video is made without it. Each slide lasts as long as its line. On an edit, false takes the narration off."
      +}
    • removedInput schema / properties / videoSettings / required
      Removed value: -[
      -  "videoDuration"
      -]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the embedPostId return, automatic animation with a 2:00 cap, the DESIGN-vs-MP4 cost/latency tradeoff, voiceover token consumption and best-effort fallback, and paid-plan image requirements. That is substantial context the structured fields do not carry.

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-loaded with purpose and the return value, then organized by Output/Motion/Defaults/Next-steps. It is dense but each section carries information; the repeated "the video is animated without asking" line is slight redundancy.

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?

With 8 params, nested videoSettings/generateImages, an output schema and full annotation coverage, the description covers the remaining gaps: the slide/scene constraint, motion timing, and images being best-effort and quota-gated. Nothing essential to correct invocation is missing.

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 schema already documents every parameter and baseline is 3. The description adds real meaning on top: the scene/slide structure rule, that motionStyle accepts built-in or saved styles discoverable via list_motion_styles/list_motion_sequences, and the timing behavior of the video.

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 first sentence gives a specific verb and resource ("Create a video post ... from your own scene content") and implicitly distinguishes it from the AI-authored generate_video sibling. An agent can identify what it does and how it differs from a one-shot generation tool.

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?

It routes the agent explicitly: use postnitro_check_status + postnitro_get_output to monitor, or postnitro_import_video_and_wait for one step, and explains the optional defaults via postnitro_set_defaults. It does not spell out when to prefer generate_video over import_video, leaving the AI-vs-own-content distinction to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources