HikerAPI — Instagram MCP

get_v2_media_info_by_code

Read-only

Retrieve an Instagram post or reel by its shortcode (the code after /p/ or /reel/) and return the media object. Returns 404 if deleted or unavailable.

Instructions

Get an Instagram post or reel by its shortcode (the part after /p/ or /reel/ in the link). Use get_v2_media_info_by_url when you have a full link and get_v2_media_info_by_id for a numeric media id. Returns the media object, or 404 for deleted or unavailable posts; promoted (ad) posts may also return 404. User tags are not included for videos, use get_gql_media_usertags for those. Live request to Instagram, billed per call. (GET /v2/media/info/by/code)

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": {
      "code": "<code>"
    },
    "name": "get_v2_media_info_by_code"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes
`safe_int`	No	Convert all big integers to strings

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.1Oct 5, 2026

addedInput schema / properties / safe_int

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Convert all big integers to strings",
+  "title": "Safe Int"
+}

First observedv1.0.2May 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover readOnly/openWorld/destructive=false, but the description adds substantial extra context: 404 for deleted/unavailable and promoted posts, user tags absent for videos, and that this is a live billed request. Error and cost behavior are disclosed beyond what annotations provide.

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?

Front-loaded purpose, then alternative routing, then behavioral caveats and billing, ending with the endpoint. Dense but every sentence carries distinct, useful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, no-output-schema tool, the description covers input meaning, sibling routing, error cases, and cost. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is only 50% (safe_int documented, code not). The description compensates by defining 'code' as the shortcode segment after /p/ or /reel/, which is meaningfully more than the schema's bare string title. It doesn't elaborate on safe_int, but the schema already does.

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 (Get) plus resource (Instagram post or reel) and clarifies the key input ('shortcode, the part after /p/ or /reel/'). It explicitly distinguishes itself from get_v2_media_info_by_url and get_v2_media_info_by_id, so an agent can route correctly without opening schemas.

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?

Gives explicit alternatives keyed to input form: use by_url for a full link, by_id for a numeric media id, and get_gql_media_usertags for user tags on videos. This is when-to-use-this vs when-to-use-siblings guidance with concrete conditions.

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

Deploy Server