Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

user_unfollow

Destructive

Stop following a specified Instagram account through a signed-in Chrome session. Triggers Instagram's in-app confirmation dialog and honors dry-run mode to prevent unintended write actions.

Instructions

Unfollow seorang user (dengan dialog konfirmasi IG). 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_unfollow"
  }
}

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?

Annotations already declare readOnlyHint=false and destructiveHint=true, but the description adds real context beyond them: the call triggers an in-app IG confirmation dialog, and IG_DRY_RUN=true downgrades it to a non-mutating run. That is exactly the kind of operational detail the annotations cannot express, though the actual effect on the target's follower list goes unstated.

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 short sentences, front-loaded with the action and immediately followed by the two behavioral caveats that matter most. Nothing is redundant and no sentence fails to earn its place.

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 one-parameter destructive tool with no output schema, the description covers the important operational facts (confirmation flow, dry-run override). The only material gap is the expected format of the username argument, which is the sole input an agent must supply.

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?

There is a single required parameter at 0% schema description coverage, so the description carries the full burden of explaining it — and it says nothing about whether username is a handle, whether it needs an '@' prefix, or whether a user ID is acceptable. An agent must guess the accepted format.

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 states a specific verb and resource ('Unfollow seorang user'), which is unambiguous and inherently distinguishes it from the user_follow sibling. It stops short of naming the counterpart tool or scoping the target type, but an agent can tell what it does without opening the schema.

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 context is only implied: the tool is for unfollowing a single user, and it notes a confirmation dialog will appear. There is no explicit statement of when to prefer this over alternatives or what preconditions hold (e.g. must already be following), leaving guidance at the minimum-viable level.

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