Skip to main content
Glama
Sign In
HikerAPI — Instagram MCP

HikerAPI — Instagram MCP

by subzeroid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v2_user_highlights_by_username

Read-only

List an Instagram user's story highlights by username, one page per call. Use when you have a handle but not the user ID; paginate with next_page_id as page_id.

Instructions

List an Instagram user's story highlights by username, one page per call. Use it only when you have a handle and not the user id: it is slower than get_v2_user_highlights and billed as 3 requests per call instead of 2. For the next page pass next_page_id from the previous response as page_id. Live request to Instagram. (GET /v2/user/highlights/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_highlights_by_username"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoSkip account privacy check
amountNoDeprecated and ignored. Use page_id / next_page_id to paginate.
page_idNoUse value of field `next_page_id` from response for getting next page
safe_intNoConvert all big integers to strings
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.1
    • addedInput schema / properties / amount / deprecated
      Added value: +true
    • addedInput schema / properties / amount / description
      Added value: +"Deprecated and ignored. Use page_id / next_page_id to paginate."
    • addedInput schema / properties / page_id
      Added value: +{
+  "default": "",
+  "description": "Use value of field `next_page_id` from response for getting next page",
+  "title": "Page Id",
+  "type": "string"
+}
    • 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.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds genuinely new operational context: it is a live Instagram request, it is slower than the id-based sibling, and it is billed at 3 requests per call instead of 2. Cost and latency disclosure is exactly the kind of behavior annotations cannot express.

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 short sentences, front-loaded with what the tool does, then the selection rule, then the pagination mechanism. No filler; every clause carries either routing or invocation information.

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?

There is no output schema, so the description supplies the return-value dependency needed to paginate (the next_page_id field). Combined with the cost/latency note and the routing rule, an agent has everything required to call it correctly and decide when not to.

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 80%, so most parameters are documented in the schema, but the description adds the cross-parameter workflow the schema cannot: passing next_page_id from the previous response as page_id. It does not explain force, safe_int, or the deprecated amount, leaving those to the schema.

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 ('List an Instagram user's story highlights by username') plus the pagination scope ('one page per call'). It explicitly differentiates itself from the sibling get_v2_user_highlights, so an agent can route without opening either 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?

Gives an explicit when-to-use rule ('only when you have a handle and not the user id') and names the preferred alternative for the id case. It also states how to paginate via next_page_id, covering the follow-up invocation path.

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