mcp-max-messenger

Remove Member

remove_member

Remove a user from a group chat. Optionally block them from rejoining. The bot must be an admin of the chat.

Instructions

Remove a user from a group chat. The bot must be an admin of the chat. Optionally block the user from rejoining. WARNING: If the user has privacy mode enabled in MAX settings, the bot will not be able to re-add them after removal — confirm with the user before proceeding.

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": {
      "chat_id": "<chat_id>",
      "user_id": "<user_id>"
    },
    "name": "remove_member"
  }
}

Input Schema

Name	Required	Description
`chat_id`	Yes	The chat_id of the group chat
`user_id`	Yes	The user_id of the member to remove
`block`	No	Block user from rejoining the chat (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.2Jun 21, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses admin requirement, optional block, and a privacy mode warning that affects re-add capability. It omits success/error responses but covers key behavioral traits.

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?

Three sentences, each serving a distinct purpose: core action, prerequisite, warning. Front-loaded and concise with no wasted words.

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?

The description covers core action, prerequisite, and a critical warning. Lacks return value information and error conditions, but is adequate for a removal tool given no output schema.

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 coverage is 100%, so the schema already documents parameters. The description adds minimal extra meaning (e.g., 'optionally block' for the block parameter) but does not deepen understanding beyond the 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 description clearly states the specific action: 'Remove a user from a group chat.' It identifies the resource (user) and context (group chat), and distinguishes from siblings like add_members and remove_admin.

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?

The description includes a prerequisite (bot must be admin) and a warning, but does not explicitly compare to alternatives like remove_admin. It indirectly suggests when to use but lacks explicit exclusions.

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