HikerAPI — Instagram MCP

get_v2_user_by_username

Read-only

Fetch an Instagram profile by username without @, returning the user object and numeric pk for other user tools. Use when you have a handle instead of a numeric user ID.

Instructions

Get an Instagram profile by username (without @). Use it when you have a handle; use get_v2_user_by_id when you already know the numeric user id (faster), and get_gql_user_about for the "About this account" panel. Returns the user object; pass its pk as the user id to the other user tools. Live request to Instagram, one billed request per call. (GET /v2/user/by/username)

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": "get_v2_user_by_username"
  }
}

Input Schema

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

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 declare the safety profile (readOnly, non-destructive, openWorld), and the description adds behavior that annotations cannot convey: it is a live request to Instagram, costs one billed request per call, and returns a user object whose pk feeds downstream tools. Cost and live-request semantics are exactly the kind of context annotations miss.

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?

Four compact sentences, front-loaded with the tool's purpose, then routing alternatives, then return/behavior notes, then the endpoint. 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 two-param read tool with no output schema, the description covers purpose, input format, alternatives, return object, chaining, cost, and endpoint. Nothing an agent needs to call 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 50%: username has no schema description but is explained in the description ('without @'), while safe_int is undocumented in both the description and a thin schema entry. The 'without @' clarification compensates for the required param's otherwise bare name, so this sits above the 3 baseline despite the coverage gap.

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 username) and explicitly distinguishes itself from get_v2_user_by_id and get_gql_user_about. The '(without @)' clarifies the input format place. An agent can route between username-based, id-based, and about-panel tools without ambiguity.

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 when-to-use ('when you have a handle'), names two alternatives with their selection conditions ('when you already know the numeric user id (faster)', 'for the About this account panel'), and adds a downstream chaining hint ('pass its pk as the user id to the other user tools'). This is close to ideal routing guidance.

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

Deploy Server