insta-pilot

ig_publish_reel

Publish a 9:16 MP4 Reel to an Instagram professional account, wait for processing, and return the public permalink.

Instructions

Publica un reel (MP4 vertical 9:16, 3s–15min). Espera a que Instagram procese el vídeo y devuelve el permalink.

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": {
      "video": "<video>"
    },
    "name": "ig_publish_reel"
  }
}

Input Schema

Name	Required	Description
`cover`	No	Imagen de portada (URL o ruta)
`video`	Yes	URL pública o ruta local (local requiere INSTA_PILOT_BLOB_TOKEN)
`account`	No	Usuario de Instagram configurado (por defecto la cuenta activa)
`caption`	No
`dry_run`	No	true = solo muestra lo que haría, sin ejecutar
`audio_name`	No
`location_id`	No
`thumb_offset`	No	ms del frame de portada si no hay cover
`collaborators`	No
`share_to_feed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: the call blocks until Instagram finishes processing the video and returns a permalink. It does not mention failure modes, quota limits, or that Instagram publishing is a two-step container flow.

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?

One sentence, front-loaded with the action and the hard format constraints, ending with the observable outcome (permalink). No filler, no restated tool name, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation with no output schema and 50% schema coverage, the description covers the critical constraint on the required video param and the return value, but omits account selection, caption limits, collaborators, cover/thumb interaction, and dry_run as a preview path. Adequate but clearly short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% across 10 parameters, so the description would need to carry weight — yet it explains none of cover, caption, account, dry_run, audio_name, location_id, thumb_offset, collaborators or share_to_feed. The format constraints only indirectly constrain "video". Baseline is not earned; the description adds little parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Publica") and resource ("reel") plus the media format constraints (MP4 vertical 9:16, 3s–15min). The resource name makes it distinguishable from ig_publish_image, ig_publish_carousel and ig_publish_story, though it never explicitly contrasts itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says what it publishes but never when to choose it over ig_publish_image/ig_publish_carousel/ig_publish_story, nor does it mention prerequisites (connected account, publishing quota). The only implicit guidance is the format constraint, which is a validation rule rather than usage routing.

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