Skip to content
Eden Engine

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.

activeper callv1
Provider
Web & Business Data Network
Category
instagram
Provider price
$0.004095 per call
Latency p50 / p95
— / —
Success rate
Verified

Provider list price; Omnial MCP charges provider cost plus a platform markup on top.

Contract

input_schema.json
{
  "type": "object",
  "required": [
    "keyword"
  ],
  "properties": {
    "keyword": {
      "type": "string",
      "examples": [
        "paris"
      ],
      "description": "Search keyword"
    }
  },
  "additionalProperties": false
}
output_schema.json
{
  "type": "object",
  "properties": {
    "data": {
      "type": "object",
      "properties": {
        "count": {
          "type": "number",
          "description": "30 on all three real fixtures observed; never confirmed as anything else."
        },
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "id": {
                "type": "string",
                "description": "The location's numeric place id as a string. Confirmed to be a place identifier, not a phone number, by matching against `facebook_places_id` on the same item across all three fixtures."
              },
              "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 real fixture item carried a corrupted-looking token string here instead of a place name (see `data.items[].name` in verification.notes)."
              },
              "address": {
                "type": "string",
                "description": "The location's street address, or an empty string when the location has none on file (observed on the majority of items in every fixture)."
              },
              "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": "Observed as the literal string 'facebook_places' on every item in every fixture."
              },
              "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, confirmed by cross-checking against `id` across all three fixtures."
              }
            },
            "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, as returned at routing.responseResultPath ($.output).",
  "additionalProperties": true
}

Pricing

Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.

Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.

ChargeRate
Per call
Flat, regardless of what comes back
$0.004095
Cost basis
Not recorded

This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.

Updated
Sep 8, 2026