Skip to main content
Glama
subzeroid

HikerAPI — Instagram MCP

by subzeroid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v2_fbsearch_topsearch

Read-only

Search Instagram for top content by keyword for a broad first look before drilling into accounts, reels, or hashtags. Paginate with next_max_id from the previous response.

Instructions

Search Instagram for top content by keyword. Use it for a broad first look; use get_v2_fbsearch_accounts to search only accounts, get_v2_fbsearch_reels only reels and get_v1_search_hashtags only hashtags. Paginate with next_max_id from the previous response. Live request to Instagram, billed per call. (GET /v2/fbsearch/topsearch)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
safe_intNoConvert all big integers to strings
next_max_idNo

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 cover safety (readOnly, non-destructive, openWorld). The description adds pagination mechanism ('Paginate with next_max_id'), cost model ('billed per call'), and endpoint nature ('Live request to Instagram')—genuine behavioral context beyond annotations. Doesn't cover rate limits or error behavior, so not a 5.

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 sentences, front-loaded with purpose, then routing, then pagination/cost. Every sentence earns its place; zero filler.

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?

Given no output schema and 33% param coverage, the description covers purpose, alternatives, pagination, and billing—most of what an agent needs. It stops short of describing return shape (top results structure) or query syntax, minor gaps for a search tool.

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 only 33%, and the description explains next_max_id usage for pagination (which is the one parameter the schema leaves undocumented beyond its title). 'safe_int' and 'query' are not elaborated in the description. Baseline 3 given the partial schema coverage and the useful next_max_id hint.

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 ('Search Instagram for top content by keyword') and explicitly differentiates from three named siblings (accounts, reels, hashtags). An agent can select this tool over get_v2_fbsearch_accounts/reels without opening any 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?

Explicit routing: 'Use it for a broad first look' paired with three named alternatives and the narrowing condition ('search only accounts', 'only reels', 'only hashtags'). Provides both when-to-use and when-to-use-alternatives.

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