Instadata — Instagram Data API

Get an account profile

get_profile

Read-onlyIdempotent

Profile, page or channel record for a public account: follower and subscriber counts, bio, and totals. Instagram only. Credits: 1 per call. Input: handle.

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": {
      "handle": "<handle>"
    },
    "name": "get_profile"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	Yes	Account handle, without the @.

Output Schema

Name	Required	Description
`data`	Yes	The endpoint's payload: one object, or an array for list calls.
`meta`	No	count, limit and next_cursor on list calls; credits_charged, credits_remaining and cache (hit or miss) on billed calls; limit_clamped when fewer items were requested upstream than the balance could cover; limit_capped when a free account's request was lowered to the free tier's 5-item ceiling.
`request_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the platform restriction (Instagram only) and the credit cost per call, both of which affect whether and how often an agent invokes it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the returned resource and kept to a few telegraphic fragments with no wasted prose. The clipped phrasing ('Input: handle') is slightly redundant given the schema but costs little.

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?

With an output schema present, return-value detail is unnecessary, and the definition covers platform scope, cost, and input. For a one-parameter read tool this is nearly sufficient; only the sibling-selection guidance is missing.

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 100% and the single handle parameter is fully documented in the schema ('without the @'). The description's 'Input: handle' merely restates the parameter name without adding format or resolution semantics, so this sits at the baseline.

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?

Names the resource precisely — the profile/page/channel record for a public account — and enumerates the payload (follower and subscriber counts, bio, totals). It does not explicitly contrast itself with siblings like get_channel_posts or get_summary, so an agent must still infer that this is the account-level lookup, but the get+profile pairing is unambiguous.

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?

'Instagram only' is an explicit scope restriction and 'Credits: 1 per call' signals cost, which helps an agent decide whether to spend a call. However, there is no statement of when to prefer this over get_summary or get_channel_posts, so the alternative-selection guidance is only implied.

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

All Instadata — Instagram Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?