Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

user_follow

Destructive

Follow an Instagram user by username and report the resulting Following or Requested state without duplicating follow requests.

Instructions

Follow seorang user. Idempotent: state Following/Requested dilaporkan apa adanya. AKSI TULIS kecuali IG_DRY_RUN=true.

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_follow"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses idempotent behavior, that the resulting state (Following vs Requested, i.e. private accounts) is reported as-is, and the IG_DRY_RUN escape hatch for suppressing the write. Annotations already flag a write/destructive open-world operation, so this adds real context rather than repeating it. It still omits error behavior for unknown usernames or rate limiting.

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?

Three short clauses with the action front-loaded and the idempotency caveat immediately after. Dense and waste-free, though the terse mixed Indonesian/English phrasing and bare IG_DRY_RUN token reduce immediate readability.

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?

With no output schema, the description does a decent job of explaining what state is returned, and the dry-run note is important for a write tool. It still leaves out authentication requirements and failure modes, which matter for an external-API mutation.

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?

Only one parameter (username) with 0% schema description coverage, and the description adds nothing about format such as whether an @ prefix or user ID is expected. The parameter name is largely self-explanatory, but the missing format detail is a real gap.

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 ("Follow seorang user"), so the agent immediately knows the action. It does not explicitly name user_unfollow as the counterpart, but the verb is unambiguous against the sibling list.

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?

Usage is only implied by the action itself; there is no statement of when to prefer this over alternatives or of prerequisites. The idempotency note implicitly tells the agent that repeat calls are safe, which is useful but not framed as guidance.

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