A2UI Atomic Catalog

unlink_slack_account

DestructiveIdempotent

Revoke one or more Slack accounts' link to this reader's store, from the Workspace side (the reverse of the Slack-side /a2ui unlink command — see slack-compiler/DESIGN-identity.md, "many Slack -> one sub"). Removes that account's ability to post via render_reading_to_slack or resolve to this reader; everything else about the reader's account is untouched. Takes an array so the Workspace's multi-select can revoke a batch in one call.

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": {
      "keys": "<keys>"
    },
    "name": "unlink_slack_account"
  }
}

Input Schema

Name	Required	Description	Default
`keys`	Yes	slack_key values from the Links view, "{team_id}:{user_id}".

Output Schema

Name	Required	Description
`note`	No	Guidance for the caller.
`reason`	No	Why nothing was removed.
`removed`	No	Links removed.
`available`	Yes	False when there is no signed-in reader or the store failed.
`requested`	No	Keys requested.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the description's added value is scope: it names exactly what is lost ('ability to post via render_reading_to_slack or resolve to this reader') and what survives ('everything else about the reader's account is untouched'). It does not mention permission/auth requirements or how to re-link afterwards, which would strengthen a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and single-paragraph, but the parenthetical internal design-doc reference and the 'many Slack -> one sub' aside add no decision-relevant information for an agent and lengthen an otherwise short instruction.

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 destructive, idempotent tool with an output schema and fully documented parameters, the description covers direction, effect, non-effect, and batch rationale. Missing only operational context such as required permissions or how to recover a revoked link.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: why it takes an array at all (the Workspace's multi-select batch). The key format is left entirely to the schema, which already documents it.

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?

States a specific verb and resource ('Revoke ... Slack accounts' link to this reader's store') and pins the direction explicitly as 'from the Workspace side (the reverse of the Slack-side /a2ui unlink command)'. An agent can distinguish it from render_reading_to_slack and other siblings 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 Guidelines4/5

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

Makes clear this is the Workspace-side revoke path as opposed to the Slack-side slash command, and that the array form exists for the UI's multi-select batch revocation. It does not spell out when not to use it (e.g. when the user just wants to stop posting, which might be handled elsewhere), so it falls short of full when/when-not guidance.

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

All A2UI Atomic Catalog tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.