Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

story_view

Destructive

Open an Instagram user's story by username and report a brief summary of its contents; viewing marks it as seen.

Instructions

Buka story seorang user dan laporkan isinya secara ringkas. EFEK: story tertanda sudah dilihat.

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": {
      "username": "<username>"
    },
    "name": "story_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The description discloses a real side effect not spelled out by the annotations – the story becomes marked as viewed – which explains the destructiveHint=true and readOnlyHint=false flags. However, with annotations already covering the safety profile, it adds little else: no mention of whether viewing is reversible, no auth or rate-limit context. It says nothing that contradicts the annotations, so there's no annotation-contradiction issue.

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?

Two short sentences, action first, effect second. No filler or repetition.

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?

For a one-parameter tool with no output schema, the description covers the essential pieces: what it does, what it returns at a high level ('laporkan isinya secara ringkas'), and the persistent side effect. The remaining gap is parameter format, which is the one thing an agent could get wrong when calling it.

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 0% for the single username parameter, so the description is the only source of meaning – but it supplies none: no format (with or without @), no indication of whether a user ID is also accepted. It only implies the value identifies the target user. Baseline 3 for a lightly parameterized tool is defensible, but the gap is real.

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?

The description gives a concrete verb-plus-resource pair ('Buka story seorang user dan laporkan isinya') that an agent can map directly to the operation, and it is clearly distinct in kind from story_create, story_delete, or stories_tray. It stops short of naming or contrasting any sibling, so it does not fully earn a 5.

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?

Usage is only implied: the agent must infer that this is the tool for reading an individual user's story rather than browsing the tray (stories_tray) or fetching posts. There is no explicit when-to-use, when-not-to-use, or prerequisite statement.

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