instagram-mcp

remove_account

Remove a configured Instagram account and securely delete its stored authentication token from the keychain.

Instructions

Remove a configured account + delete its stored token from the keychain.

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": {
      "label": "<label>"
    },
    "name": "remove_account"
  }
}

Input Schema

Name	Required	Description	Default
`label`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden and does explicitly disclose the destructive keychain-token deletion. However, it does not state that the action is irreversible, what happens to related account state, or whether permissions are required, so transparency is only partial.

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 a single tightly written sentence with no filler, and the primary action is front-loaded. Every word contributes to the tool's meaning.

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?

For a destructive one-parameter tool, the description states the core behavior and the keychain side effect, and an output schema exists to cover return values. Still, it omits important practical context like finding valid labels via list_accounts and any default-account removal constraints.

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?

The schema provides zero description coverage for the single required 'label' parameter, and the description does not explain what label values are valid, how to obtain them, or that list_accounts can supply them. The phrase 'configured account' hints at the label but does not add real parameter-level 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?

The description names a clear verb ('Remove') and a specific resource ('a configured account'), and adds the concrete side effect of deleting its stored token from the keychain. This cleanly distinguishes it from sibling tools like add_account, list_accounts, and set_default_account.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives, no mention that it complements list_accounts/add_account, and no note about constraints such as whether the default account can be removed. The context is implied only by the wording 'configured account.'

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