wechat-mcp

Log out / remove a WeChat account

wechat_logout

Remove a logged-in WeChat account by deleting its credentials, sync buffer, and cached tokens. Provide the account ID from wechat_list_accounts.

Instructions

Remove a logged-in WeChat account: deletes its stored credentials, sync buffer, and cached context tokens. Provide the accountId from wechat_list_accounts.

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": "wechat_logout"
  }
}

Input Schema

Name	Required	Description	Default
`accountId`	Yes	Account id to remove (see wechat_list_accounts).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Without annotations, the description fully bears the burden. It discloses that the tool deletes stored credentials, sync buffer, and cached context tokens, giving clear insight into the destructive actions. It could mention irreversibility, but current detail is adequate.

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 sentences, no wasted words. The purpose and parameter source are front-loaded, making it quick to parse.

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 single-parameter tool with no output schema or annotations, the description covers the action, consequences, and parameter source. Minor omission: no mention of return value or confirmation, but sufficient given simplicity.

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 the description adds minimal new meaning beyond 'Account id to remove (see wechat_list_accounts).' It reinforces the source of the ID but does not deepen parameter understanding.

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 uses a specific verb 'Remove' and identifies the resource as 'logged-in WeChat account'. It clearly distinguishes the action from sibling tools like wechat_login (login) and wechat_list_accounts (list).

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?

The description states 'Provide the accountId from wechat_list_accounts', indicating a prerequisite for using this tool. However, it does not explicitly mention when not to use it or suggest alternatives, though the context of sibling tools implies distinct use cases.

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

Deploy Server