HikerAPI — Instagram MCP

get_v1_location_search

Read-only

Retrieve Instagram locations at a given coordinate. Pass latitude and longitude to search by location instead of name.

Instructions

Find Instagram locations at a coordinate: pass lat and lng. Use get_v1_fbsearch_places to search places by name instead. Live request to Instagram, billed per call. (GET /v1/location/search)

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "get_v1_location_search"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes
`lng`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2May 1, 2026

TDQS

A4.6/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 the safety profile is covered. The description adds genuinely new behavioral context that annotations do not: the call is a live Instagram request and is billed per invocation, which affects how readily an agent should call it.

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 terse fragments: purpose, alternative, cost. Front-loaded, no filler, and every clause carries information an agent needs.

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 low-complexity 2-param read tool with annotations present and no output schema, the definition covers purpose, alternative routing, and cost. It does not hint at what the returned locations contain, but that is a minor gap given the simplicity.

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 0%, but the description compensates by stating that lat and lng are passed together to form a coordinate, giving the parameters meaning beyond bare 'Lat'/'Lng' titles. No format details (precision, ranges, coordinate system) are supplied, keeping it short of a 5.

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?

Specific verb+resource: 'Find Instagram locations at a coordinate', completed by the required lat/lng inputs. It explicitly names the sibling it is not (get_v1_fbsearch_places) and even cites the underlying endpoint, so an agent can distinguish it without opening schemas.

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?

States the selection condition (coordinate-based lookup) and names the alternative with the condition that routes to it ('search places by name'). Also flags that it is a live, billed call, which is real decision-relevant guidance.

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

Deploy Server