Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Remove Account

remove_account
DestructiveIdempotent

Disconnect a social account from the workspace, delete its stored tokens, remove it from pending and recurring posts, and stop it counting toward the plan.

Instructions

Disconnect a social account from the workspace, the same way the Connectors page does: its stored tokens are deleted, it is taken off every pending and recurring post, and it stops counting toward the plan. Works for accounts in any status, so an unauthorized account can be cleaned up without reconnecting it. For Facebook only the named page goes; the other pages of the same login stay connected. Posts already published stay on the network. Confirm with the user first, naming the account. Bringing it back means connecting it again in AdaptlyPost (create_connect_link can send a link). Needs the accounts.manage permission, which Admin holds.

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

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe account id from list_accounts, or the Facebook pageId
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with id, platform, displayName, pageId for Facebook, and removed: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.6/5.0
Behavior5/5

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

Although annotations already flag destructiveHint=true and idempotentHint=true, the description adds substantial detail beyond them: tokens are deleted, the account is stripped from pending and recurring posts, plan counting stops, and published posts remain on the network. It also discloses the required accounts.manage permission and the Facebook-specific page-level scope.

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?

The core action and its effects are front-loaded, and every sentence carries a distinct fact (side effects, Facebook scope, reversibility, permission). It is dense but slightly long, with the reconnect note and permission note readable as separate trailing items.

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

Completeness5/5

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

For a destructive two-parameter mutation with full schema coverage and an output schema, the description covers side effects, scope granularity, irreversibility path, and authorization. Nothing an agent needs before invoking it is missing.

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 description coverage is 100%, so both accountId (including the Facebook pageId variant) and workspaceId are already fully documented in the schema. The description adds only the confirmation convention rather than new parameter semantics, which fits the baseline for a well-documented schema.

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 first sentence states a specific verb and resource ("Disconnect a social account from the workspace") and anchors it to the known Connectors-page behavior. It is clearly distinct from siblings such as create_connect_link, which is named as the inverse operation.

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

Usage Guidelines5/5

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

It says explicitly when this applies (any account status, including unauthorized ones that cannot be reconnected) and gives a mandatory precondition ("Confirm with the user first, naming the account"). It also points to create_connect_link for the opposite need, so the agent has both the use case and the alternative.

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