Skip to main content
Glama

ig_publish_story

Publish an Instagram Story image or video by providing its public URL and media type. Stories automatically disappear after 24 hours.

Instructions

Publish a Story (image or video). Stories disappear after 24 hours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
media_typeYesStory media type
media_urlYesPublic HTTPS URL of the media
Behavior3/5

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

With no annotations, the description carries full burden. It adds the behavioral trait that stories disappear after 24 hours, but fails to disclose authentication requirements, rate limits, or success/error responses. This is adequate but not thorough.

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?

The description is extremely concise with two sentences, no filler, and front-loaded key information. Every word earns its place.

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?

Despite simplicity (2 params, no output schema), the description covers purpose, media types, and lifespan. It lacks only common context like required account type or post limits, but overall complete for a straightforward publish action.

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 description coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema: 'image or video' mirrors the enum, and 'Public HTTPS URL' is already in the schema's description. No additional parameter meaning is provided.

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 verb 'Publish' and the resource 'Story', specifies media types (image or video), and adds unique context that stories disappear after 24 hours, distinguishing it from feed-related siblings like ig_publish_photo.

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

Usage Guidelines3/5

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

The description implies usage for stories but does not explicitly guide when to use this tool versus alternatives like ig_publish_photo (feed) or ig_publish_reel. No when-not-to-use or alternative references are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server