Skip to main content
Glama
billyfranklim1

mcp-evolution

Update Block Status

update_block_status

Block or unblock a WhatsApp contact by specifying their phone number or JID and the desired status.

Instructions

Block or unblock a WhatsApp contact via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesRecipient JID or phone number (e.g. 5511999999999 or group@g.us)
statusYesblock: block the contact; unblock: unblock the contact

Implementation Reference

  • Handler function that registers the 'update_block_status' MCP tool. It calls Evolution API endpoint /chat/updateBlockStatus/{instanceName} with number and status (block/unblock) parameters.
    export function registerUpdateBlockStatus(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "update_block_status",
        {
          title: "Update Block Status",
          description: "Block or unblock a WhatsApp contact via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(`/chat/updateBlockStatus/${client.instanceName}`, {
              number: args.number,
              status: args.status,
            });
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (e) {
            if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
            throw e;
          }
        }
      );
    }
  • Input schema defining the 'number' parameter (phone or JID) and 'status' parameter (enum: block/unblock) for the tool.
    const schema = {
      number: PhoneOrJidSchema,
      status: z.enum(["block", "unblock"]).describe("block: block the contact; unblock: unblock the contact"),
    };
  • Registration call that wires the update_block_status tool into the MCP server via registerAllTools().
      registerUpdateBlockStatus(server, client);
      registerCheckNumber(server, client);
    }
  • Shared Zod schema for phone number or JID, used by the 'number' parameter of update_block_status.
    export const PhoneOrJidSchema = z
      .string()
      .min(1)
      .describe("Recipient JID or phone number (e.g. 5511999999999 or group@g.us)");
Behavior2/5

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

The description is too brief and fails to disclose behavioral traits beyond the basic action. With no annotations, it should mention what blocking entails (e.g., prevents messages), reversibility, or any side effects.

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?

Very concise (one sentence) and front-loaded with the action. However, it is too minimal; more detail could be added without losing conciseness.

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

Completeness2/5

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

Lacks context for a simple tool. No output schema, no description of return value or error handling. Additional details like 'returns success/failure' or 'affects sending messages' would improve completeness.

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%, and schema descriptions already clarify the parameters (number format, status enum meanings). The tool description adds no extra semantics, so baseline 3 is appropriate.

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?

Description clearly states 'Block or unblock a WhatsApp contact via the pinned instance', which is a specific action on a specific resource. It distinguishes from sibling tools by focusing on blocking/unblocking, a unique operation among many messaging and management tools.

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?

No guidance on when to use this tool versus alternatives (e.g., check_number, update_participants). No mention of prerequisites like needing the instance to be connected or contact existing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/billyfranklim1/mcp-evolution'

If you have feedback or need assistance with the MCP directory API, please join our Discord server