Skip to main content
Glama
Sign In
upload-post-mcp

upload-post-mcp

by MrSagarShah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Instagram post comments

get_comments

Retrieve comments from an Instagram post or reel. Provide the post ID or URL, paginate using the cursor from the previous response.

Instructions

Retrieve comments on an Instagram post/reel. Provide post_id or post_url. Paginate with the returned next_cursor.

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

Input Schema

NameRequiredDescriptionDefault
userYesUpload-post profile identifier.
afterNoPagination cursor from the previous response.
limitNoComments per page (max 50).
post_idNoNumeric Instagram media ID.
post_urlNoFull Instagram post or reel URL (alternative to post_id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations present; description mentions pagination and read-like behavior, but lacks details on authentication, rate limits, or response format.

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?

Two concise sentences front-loading purpose followed by usage; no unnecessary words.

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

Completeness3/5

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

Covers retrieval and pagination, but lacks output schema and does not detail what comment objects contain or prerequisite authentication.

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 covers all parameters with descriptions; description adds context on alternatives (post_id vs post_url) and pagination cursor, but adds limited new meaning.

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?

Description clearly states verb 'Retrieve' and resource 'comments on an Instagram post/reel', and distinguishes from siblings like reply_to_comment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides clear usage instructions (provide post_id or post_url, paginate with next_cursor), but no explicit when-not-to-use or alternatives.

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

Deploy Server

Other Tools