Skip to main content
Glama

list_live_stories

Read-onlyIdempotent

List the stories that are live on Instagram right now (the ~24h window).

Use this to scope a story-reply automation to one specific story: pick the story with the user, then pass its ig_media_id as post_ids to create_automation / update_automation with trigger_type="story_reply" and post_target="specific". An empty list means nothing is up right now.

Only stories still live are returned — Instagram drops the rest at ~24 hours. For how earlier ones performed use get_story_analytics, which only has stories captured while they were live.

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>"
    },
    "name": "list_live_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds genuine context beyond that: only currently-live stories are returned, Instagram drops them at ~24h, and an empty list has a defined meaning ('nothing is up right now'). It does not mention pagination, ordering, or rate limits, so it stops short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short paragraphs, front-loaded with the what and the 24h scope, then the workflow, then the exclusion. Every sentence carries information the agent needs; nothing is 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?

Output schema exists, so return contents need no explanation, and the description covers the empty-result case and the data lifetime, which is the non-obvious part. The remaining gap is that the two required identifiers are never characterized, which matters for a tool that is scoped to one account.

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

Parameters2/5

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

Schema description coverage is 0% and both required parameters (workspace_id, ig_account_id) are undocumented in either the schema or the description. The description mentions ig_media_id and post_ids, but those belong to the sibling automation tools, not to this tool's inputs, so an agent gets no added meaning for what it must actually supply.

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?

States a specific verb and resource plus the scope constraint ('stories that are live on Instagram right now (the ~24h window)'), which is exactly what separates it from get_story_analytics and list_recent_media. An agent can identify the tool's role without opening the 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 use case (scoping a story-reply automation to one story) and gives the concrete downstream call sequence: pass ig_media_id as post_ids to create_automation/update_automation with trigger_type='story_reply' and post_target='specific'. It also names the alternative for the opposite case — get_story_analytics for historical performance — so when-to-use and when-not-to-use are both covered.

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