Skip to main content
Glama

publish_story

Publish a photo or video to Instagram Stories, immediately.

media_url is one publicly fetchable image or video link; whether it's treated as a photo or a video story is detected when it's downloaded.

Stories take media and nothing else — Instagram rejects a caption, hashtags, share-to-feed and comment settings on a story, so this tool doesn't accept them. If the user asks for a captioned story, tell them the text has to be burned into the image or video itself.

This goes out now. For a story the user wants at a later time, use schedule_story — don't schedule a reel instead.

automation_id attaches a story-reply automation, so replies to this story trigger it. Stories expire after ~24 hours: list_live_stories shows the ones still up, and get_story_analytics how recent ones did.

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": {
      "workspace_id": "<workspace_id>",
      "ig_account_id": "<ig_account_id>",
      "media_url": "<media_url>"
    },
    "name": "publish_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_urlYes
client_tokenNo
workspace_idYes
automation_idNo
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault
modeYes
statusYes
post_idYes
scheduled_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the write, non-idempotent and open-world profile, and the description adds real context beyond that: media type is auto-detected at download time, coverage is ~24 hours, and automation_id wires up reply automation. It stops short of stating required account permissions or what a failed publish returns, which keeps it off a 5.

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 the action, then constraints, then lifecycle pointers — a logical order with no filler sentences. Slightly long for the amount of hard information, particularly the aside about burning text into the media, but that aside is genuine agent guidance rather than padding.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the description still points to list_live_stories and get_story_analytics for follow-up. For a publish mutation it is nearly complete; the main gap is that auth/permission prerequisites and the meaning of client_token and the two ID parameters are never addressed.

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?

With 0% schema description coverage, the description must carry all parameter meaning, but it only covers two of five: media_url ('one publicly fetchable image or video link') and automation_id ('attaches a story-reply automation'). workspace_id, ig_account_id and especially client_token are left completely unexplained in both schema and prose.

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 ('Publish a photo or video to Instagram Stories') plus an immediacy qualifier. That immediacy qualifier is exactly what separates it from schedule_story, so an agent can route without reading 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?

Explicitly states the alternative for deferred posting ('use schedule_story — don't schedule a reel instead') and rules out a real failure mode by saying stories reject captions, hashtags, share-to-feed and comment settings, including what to tell the user instead. When-to-use, when-not-to-use, and the fallback are all present.

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