instagram-data-mcp

Overview Schema Source Related Servers Discussions Admin

instagram_place

Read-only

Fetches details for an Instagram location by numeric ID, including name, category, address, city, phone, website, and post count. Find location IDs with /v1/search.

Instructions

Get an Instagram location. Name, category, address, city, phone, website and post count of a location page. Find ids with /v1/search.

Cost: 3 credits.

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": {
      "id": "<id>"
    },
    "name": "instagram_place"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Numeric location id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Sep 28, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and openness profile. The description adds meaningful operational context by stating the cost (3 credits) and enumerating the fields returned, which the annotations do not provide. It still omits error behavior, rate limits, or auth requirements.

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, front-loaded with purpose, immediately followed by return fields and id-discovery guidance, then cost as a separate terse line. No filler; every sentence earns its place.

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 single-resource getter with no output schema, the description adequately lists returned fields and explains how to find the required id. Annotations cover the safety profile. Minor gaps remain around error handling and rate limits, but the definition is largely complete for correct selection and invocation.

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 100% and the schema itself documents 'Numeric location id.' The description adds value by telling the agent how to obtain a valid id ('Find ids with /v1/search'), which is not in the schema and directly helps correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get an Instagram location') and enumerates the returned fields. It does not explicitly distinguish itself from the sibling instagram_place_posts, so an agent might still hesitate between the two 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a prerequisite ('Find ids with /v1/search') but gives no explicit when-to-use / when-not guidance or alternative routing (e.g., use instagram_place_posts for the posts themselves). Usage context is implied rather than stated.

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