Skip to main content
Glama
subzeroid

HikerAPI — Instagram MCP

by subzeroid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v2_fbsearch_accounts

Read-only

Search Instagram accounts by keyword to find profiles when the exact handle is unknown. Paginate through results using the page token.

Instructions

Search Instagram accounts by keyword. Use it to find a profile when you do not know the exact handle; use get_v2_user_by_username for an exact handle. Paginate with page_token from the previous response. Live request to Instagram, billed per call. (GET /v2/fbsearch/accounts)

Input Schema

NameRequiredDescriptionDefault
queryYes
safe_intNoConvert all big integers to strings
page_tokenNo

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 readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-derivable context: this is a live (non-cached) request to Instagram billed per call, plus the pagination contract for `page_token`. It does not disclose rate limits or what a result record contains, so it stops short of 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 short sentences, each load-bearing: purpose, routing alternative, pagination and cost. Front-loaded with the primary action and closed with the underlying endpoint. No 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?

For a read-only search endpoint with no output schema, the description covers the essentials an agent needs: what it searches, the alternative for exact handles, how to paginate, and that calls are billed. Only the `safe_int` parameter and the shape of returned account records remain undocumented.

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%, so the description has to carry more weight. It does explain keyword semantics for `query` and the pagination role of `page_token`, but adds nothing about `safe_int` beyond the schema's own thin description. Partial compensation justifies the baseline 3.

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 ('Search Instagram accounts by keyword') and immediately distinguishes itself from the closest sibling by naming `get_v2_user_by_username` for exact-handle lookups. An agent can select between the two 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?

Explicitly states when to use this tool ('when you do not know the exact handle') and names the alternative plus its selection condition. The pagination instruction adds a concrete procedural norm.

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