Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

stories_tray

Read-only

List Instagram accounts with active stories in the home tray to select which story to view.

Instructions

Daftar akun dengan story aktif di tray beranda saat ini (untuk memilih story mana yang dilihat).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stories_tray"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that results reflect the tray 'saat ini' (a live snapshot of who has active stories) and that the payload is a list of accounts, but it says nothing about ordering, pagination, or what fields each account carries.

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?

One tight sentence with the resource front-loaded and the use case in a trailing parenthetical. Nothing is padded, though the parenthetical could be phrased as an explicit next-step instruction instead.

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 simple read-only discovery tool with annotations covering safety and no output schema, the description is close to sufficient: it identifies the target set and the follow-up action. It still leaves the limit parameter and result shape (account identity fields, ordering) to inference.

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 the single parameter (limit) is never mentioned in the description, so it adds no meaning beyond the bare property name. An agent must infer that limit caps the number of returned accounts.

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+resource: lists accounts that currently have active stories in the home tray, plus the intent (choosing which story to view). This cleanly separates it from viewing/creating stories, though it never names the follow-up tool (story_view) explicitly.

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 parenthetical 'untuk memilih story mana yang dilihat' implies the workflow: call this first to discover candidates, then view one. There is no explicit when-not guidance, no mention of alternatives such as story_view or how the tray differs from other feeds.

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