Socify-mcp

instagram_media/comments

List comments on a public Instagram post or Reel (paginated, newest-first).. Platform=instagram resource=media/comments. Costs 1 credit(s) per request. Requires Authorization: Bearer <api_key>.

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": {
      "media": "<media>"
    },
    "name": "instagram_media/comments"
  }
}

Input Schema

Name	Required	Description	Default
`media`	Yes	Shortcode, post/Reel URL, or numeric media id.
`cursor`	No	Pagination cursor from a previous response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- changedInput schema / properties / media / examples
```
Previous value: -[
-  "C-6WRvdS75Q"
-]New value: +[
+  "DfAWxdIFmVB"
+]
```
AddedNov 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose non-obvious traits: newest-first ordering, cursor pagination, a cost of 1 credit per request, and the required Bearer auth header. It omits failure behavior and any rate limits, which 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?

Front-loaded single sentence with the key facts first, followed by short metadata lines. There is a minor formatting blemish (doubled period) and the credit/auth line reads as template boilerplate, but nothing is wasted.

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 two-parameter read-only list tool with no output schema and no annotations, the description covers platform scope, ordering, pagination, auth, and cost. Only edge-case behavior for private or restricted media is left unaddressed.

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%, so 'media' accepts shortcode, URL, or numeric id, and 'cursor' is already documented in the schema. The description adds only that results are paginated newest-first, which is marginal value over the schema and matches the baseline.

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

Purpose5/5

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

States a specific verb and resource (list comments on a public Instagram post or Reel) and adds ordering (newest-first) and pagination. The explicit 'Instagram' platform separates it from the sibling comment tools for TikTok and YouTube.

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?

The 'public Instagram post or Reel' scoping implies when the tool applies, but there is no explicit when-to-use guidance relative to siblings such as instagram_media/info, and no exclusions for private, deleted, or comment-disabled media.

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

All Socify-mcp 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?