Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

user_posts

Read-only

Lists a user's latest posts and reels from a profile URL, helping you research content and monitor competitor accounts.

Instructions

Daftar post/reel terbaru dari profil seorang user (URL saja). Berguna untuk riset konten & monitoring kompetitor.

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": {
      "username": "<username>"
    },
    "name": "user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing about result volume, ordering, pagination, or how 'latest' is bounded, and the parenthetical '(URL saja)' muddies the input expectation rather than clarifying behavior.

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?

Two short sentences, front-loaded with the core action, with no filler. The parenthetical '(URL saja)' is the one piece that subtracts rather than adds.

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

Completeness2/5

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

For a two-parameter tool with no output schema and no documented fields, the description should explain what 'limit' controls and what shape of post data returns. It leaves both undocumented and introduces an input-format ambiguity that could cause a wrong call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter load, but it only gestures at 'username' as '(URL saja)' — which actually conflicts with the required string parameter named 'username'. The 'limit' parameter is never mentioned at all.

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?

States a specific verb and resource: lists the latest posts/reels from a given user's profile, which separates it from feed/explore/hashtag tools by scope. It stops short of naming the closest siblings explicitly, but the scope 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?

The second sentence gives a motivating use case (content research, competitor monitoring), which implies when to reach for it. It offers no exclusions or alternatives, so an agent must infer that hashtag_posts or explore_posts are the right choice when the target is not a specific profile.

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