Instadata — Instagram Data API

Read comments on a post

get_comments

Read-onlyIdempotent

Comments on a public post or video, newest first, paginated with limit and cursor. Instagram only. Credits: 1 per item returned, and an empty result is free (25 a day per account, then 1 credit each). Input: url.

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": {
      "url": "<url>"
    },
    "name": "get_comments"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Full public URL of the post, video, profile or page.
`limit`	No	Items to return, up to 50; a larger value is lowered to 50, and free accounts get at most 5 (meta.limit_capped reports it). Credits are charged per item returned, and an empty result is free (25 a day per account, then 1 credit each).
`cursor`	No	next_cursor from a previous call's meta.

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.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety needs no restating. The description adds real value beyond them: result ordering (newest first), pagination mechanics, a per-item credit cost, a free-empty-result rule, and a 25/day per-account quota. Only the absence of auth/error behavior keeps it from a 5.

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?

Content is front-loaded: what it returns, platform scope, then pricing. Nearly every clause carries information. The trailing 'Input: url' is redundant with the required schema field and could be dropped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety and an output schema covering return values, the description supplies the remaining agent-relevant context: platform restriction, ordering, pagination, and credit/quota economics. An agent can decide and invoke correctly from this.

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 parameters are fully documented in the schema, including the 50-item maximum, the free-account cap of 5, and the meta.limit_capped reporting. The description's 'paginated with limit and cursor' and 'Input: url' merely restate schema content, adding no new meaning.

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?

The description states a specific resource and scope: comments on a public post or video, returned newest first. The 'Instagram only' qualifier further narrows it. It does not name or contrast any sibling (e.g. get_post_stats or get_channel_posts), so an agent must infer the boundary itself.

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?

There is implied guidance in 'public post or video' and 'Instagram only', which tells the agent the tool is inapplicable to private posts or other platforms. However, no explicit when-to-use-vs-alternatives statement or prerequisite (auth, public-only accounts) is given.

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?