Skip to main content
Glama
Sign In

Spaces

by com.spacesos.api
OverviewDiscussionsAdmin

Who liked a post

list_post_reactions
Read-onlyIdempotent

The people who liked (or reacted to) a post, with username, name and picture. Instagram shows at most the latest 100. Counts as browsing.

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": {
      "account_id": "<account_id>",
      "post_id": "<post_id>"
    },
    "name": "list_post_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page (1-100; Instagram follower pages hold at most 25).
cursorNonext_cursor from the previous page.
post_idYesThe post id (social_id from list_own_posts or list_user_posts).
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, open-world, and non-destructive. Beyond that, the description adds useful behavioral context: Instagram exposes at most the latest 100 reactions, and the call counts as browsing, which may matter for quota or usage tracking.

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?

The description is short and front-loaded: it states the returned people and fields, then adds the 100-item cap and browsing-cost note. Every sentence contributes useful information without repetition or filler.

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 no output schema, the description usefully identifies the return fields and the maximum number of reactions available. It is complete enough for a read-only listing tool, though it could say more about pagination behavior and the required account_id parameter.

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 75%, so the baseline is 3. The description does not add parameter-specific meaning beyond the schema; it mentions the 100-item cap, but limit, cursor, and post_id are already documented in the schema, while account_id lacks a description in both places.

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 clearly states that this tool returns people who liked or reacted to a post, including username, name, and picture. The verb and resource are specific enough to distinguish it from reactions on comments, messages, or users, though it does not explicitly name sibling alternatives.

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 description implies usage by describing the data returned for a post's reactions. However, it gives no explicit when-to-use guidance, no exclusions, and no routing to alternative reaction-list tools such as list_comment_reactions or list_user_reactions.

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

All Spaces toolsInspect
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