Skip to main content
Glama
subzeroid

HikerAPI — Instagram MCP

by subzeroid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v2_story_by_id

Read-only

Fetch a single Instagram story by its ID for direct story data retrieval. Use it when you have an ID and need one story instead of a list or URL.

Instructions

Get one Instagram story by its id. Use get_v2_story_by_url when you have a story link and get_v2_user_stories to list a user's active stories. Live request to Instagram, billed per call. (GET /v2/story/by/id)

Input Schema

NameRequiredDescriptionDefault
idYes
safe_intNoConvert all big integers to strings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • addedInput schema / properties / safe_int
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Convert all big integers to strings",
+  "title": "Safe Int"
+}
  2. First observedv1.0.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds genuinely useful context beyond that: it is a live network request to Instagram and is billed per call, which affects cost-aware invocation. Return format and failure behavior are not described, keeping it 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 tight sentences, each earning its place: purpose, routing, and cost. The primary intent is front-loaded and the endpoint path is a compact trailing annotation.

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 single-record read tool with an output schema absent but a simple return shape, the description covers routing, cost, and safety. It omits only minor detail about what is returned or error behavior, which is a small gap for a getter of this simplicity.

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 coverage is 50%: safe_int carries its own description while id does not. The description implies id is the story identifier but adds no format, type, or validation detail beyond the schema and tool name. A baseline 3 is appropriate when the schema does most of the work and the description contributes nothing param-specific.

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 ('Get one Instagram story by its id') and explicitly disambiguates from sibling tools by name. An agent can route between story-by-id, story-by-url, and user-stories without opening any 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?

Names the two alternatives explicitly with the condition that selects each: get_v2_story_by_url when you hold a link, get_v2_user_stories to list a user's active stories. This is textbook when-to-use guidance.

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

Deploy Server

Other Tools