Skip to main content
Glama
subzeroid

HikerAPI — Instagram MCP

by subzeroid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v2_track_by_id

Read-only

Fetch an Instagram music track by track_id and paginate with page_id. Use it after keyword music search to retrieve track details.

Instructions

Get an Instagram music track by track_id. Use get_v1_search_music to find tracks by keyword. For the next page pass next_page_id from the previous response as page_id. Live request to Instagram, billed per call. (GET /v2/track/by/id)

Input Schema

NameRequiredDescriptionDefault
page_idNoUse value of field `next_page_id` from response for getting next page
safe_intNoConvert all big integers to strings
track_idYes

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 readOnly/openWorld/non-destructive, so safety is covered. The description adds genuinely useful operational context beyond them: it is a live Instagram request billed per call, and it explains the pagination handoff. It stops short of describing rate limits or what a failed lookup returns.

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 front-loaded and pagination and billing details following in priority order. Every sentence carries information.

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 read-only lookup with no output schema, the description covers identity, alternative, pagination and cost. Only the safe_int parameter and any error/empty-result behavior are unaddressed.

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 67%; page_id is documented in the schema and echoed in the description, and track_id is self-evident. The third parameter, safe_int, is left unexplained in the description, so it adds little beyond the schema for a moderate-coverage case.

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'), a specific resource ('Instagram music track'), and the identifying key ('track_id'). It also distinguishes itself from the sibling get_v1_search_music, which is the keyword-search counterpart.

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?

Explicitly routes the agent: use this tool for lookup by id, use get_v1_search_music to find tracks by keyword, and pass next_page_id as page_id for the next page. Both the when and the alternative are named.

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