Instagram Location Search (by Keyword)
omnial/instagram-search-locations
Given a free-text keyword (a city, landmark, or business name), returns up to 30 matching Instagram-taggable locations, each with its place name, street address when the location has one on file, latitude/longitude, and the location's numeric place id.
Price
Up to $0.0041 per call; you pay what the call used
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.
Data source
Data from Instagram.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "omnial/instagram-search-locations" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "omnial/instagram-search-locations" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "omnial/instagram-search-locations", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "omnial/instagram-search-locations", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0041 |
- Updated
- Oct 25, 2026
Input and output schemas
Input schema
{
"type": "object",
"required": [
"keyword"
],
"properties": {
"keyword": {
"type": "string",
"examples": [
"paris"
],
"description": "Search keyword"
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"properties": {
"data": {
"type": "object",
"properties": {
"count": {
"type": "number",
"description": "Typically 30."
},
"items": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "The location's numeric place id as a string. A place identifier, not a phone number; often matches `facebook_places_id` on the same item."
},
"city": {
"type": "string",
"description": "Often an empty string; populated on only a minority of items observed."
},
"name": {
"type": "string",
"description": "The location's public tag label. Free text supplied by whoever originally tagged the place, so it is not guaranteed to describe a physical place at all -- one observed item carried a corrupted-looking token string here instead of a place name."
},
"address": {
"type": "string",
"description": "The location's street address, or an empty string when the location has none on file (the case for the majority of items)."
},
"latitude": {
"type": "number",
"description": "Absent entirely (not null) on at least one item observed (a location with no coordinates on file)."
},
"longitude": {
"type": "number",
"description": "Absent entirely (not null) on at least one item observed, always paired with a missing `latitude`."
},
"short_name": {
"type": "string",
"description": "A shorter form of `name`, same free-text caveat."
},
"external_source": {
"type": "string",
"description": "Typically the literal string 'facebook_places'."
},
"facebook_places_id": {
"type": "number",
"description": "The location's numeric Facebook Places id. Frequently identical to `id` (as a number vs. a string) but sometimes differs -- both are plain place identifiers, not a phone number."
}
},
"additionalProperties": true
},
"description": "Never empty on any of the three real calls observed (including two nonsense keywords) -- an empty-results case is UNCONFIRMED."
}
},
"additionalProperties": true
}
},
"description": "The location search result.",
"additionalProperties": true
}