HikerAPI — Instagram MCP

get_v2_user_by_id

Read-only

Fetch an Instagram profile by numeric user ID when you already have the ID from another tool. Returns the user object via a live, billed API request.

Instructions

Get an Instagram profile by numeric user id. Use it when you already have the id from another tool; use get_v2_user_by_username when you only have a handle. Returns the same user object. Live request to Instagram, billed per call. (GET /v2/user/by/id)

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": {
      "id": "<id>"
    },
    "name": "get_v2_user_by_id"
  }
}

Input Schema

Name	Required	Description	Default
`id`	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.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. The description adds genuinely useful context beyond them: it is a live request to Instagram and is billed per call, which affects agent invocation strategy. It also notes the return is the same user object as the username variant.

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 sentences, no filler, with the core purpose and the sibling routing front-loaded and the billing caveat last.

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 simple two-parameter lookup with no output schema, the definition covers what the tool does, when to use it, what it returns, and its cost profile. The only minor gap is the undocumented safe_int parameter, which is unaddressed in both schema and description.

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 is documented inline but id is not. The description adds 'numeric user id,' which clarifies the id parameter's expected form, but nothing is said about safe_int or its behavior. Baseline 3 given partial schema coverage and the marginal added value.

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+resource: 'Get an Instagram profile by numeric user id.' It also names the sibling it is not (get_v2_user_by_username) so the agent can distinguish the two 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?

Explicit routing: 'Use it when you already have the id from another tool; use get_v2_user_by_username when you only have a handle.' Both the when and the alternative are spelled out.

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

Deploy Server