Skip to main content
Glama
billyfranklim1

mcp-evolution

Update Privacy Settings

update_privacy

Update privacy settings for a WhatsApp instance, controlling who can see read receipts, profile, status, online status, last seen, and who can add to groups or call.

Instructions

Update privacy settings for the pinned WhatsApp instance. Values: all, contacts, contact_blacklist, none.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
readreceiptsNoWho can see read receipts
profileNoWho can see the profile picture
statusNoWho can see status updates
onlineNoWho can see online status
lastNoWho can see last seen
groupaddNoWho can add to groups
calladdNoWho can call

Implementation Reference

  • The registerUpdatePrivacy function registers and implements the 'update_privacy' tool handler. It builds a payload from optional privacy fields (readreceipts, profile, status, online, last, groupadd, calladd) and sends a POST request to Evolution API endpoint /chat/updatePrivacySettings/{instanceName}.
    export function registerUpdatePrivacy(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "update_privacy",
        {
          title: "Update Privacy Settings",
          description: "Update privacy settings for the pinned WhatsApp instance. Values: all, contacts, contact_blacklist, none.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const payload: Record<string, unknown> = {};
            if (args.readreceipts !== undefined) payload["readreceipts"] = args.readreceipts;
            if (args.profile !== undefined) payload["profile"] = args.profile;
            if (args.status !== undefined) payload["status"] = args.status;
            if (args.online !== undefined) payload["online"] = args.online;
            if (args.last !== undefined) payload["last"] = args.last;
            if (args.groupadd !== undefined) payload["groupadd"] = args.groupadd;
            if (args.calladd !== undefined) payload["calladd"] = args.calladd;
            const data = await client.post(`/chat/updatePrivacySettings/${client.instanceName}`, payload);
            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;
          }
        }
      );
    }
  • Zod schema definitions for the 'update_privacy' tool. PrivacyValueSchema is an enum of 'all', 'contacts', 'contact_blacklist', 'none'. The input schema defines optional fields: readreceipts, profile, status, online, last, groupadd, calladd.
    import { z } from "zod";
    import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
    import { McpError } from "@modelcontextprotocol/sdk/types.js";
    import type { EvolutionClient } from "../evolution-client.js";
    
    const PrivacyValueSchema = z.enum(["all", "contacts", "contact_blacklist", "none"]);
    
    const schema = {
      readreceipts: PrivacyValueSchema.optional().describe("Who can see read receipts"),
      profile: PrivacyValueSchema.optional().describe("Who can see the profile picture"),
      status: PrivacyValueSchema.optional().describe("Who can see status updates"),
      online: PrivacyValueSchema.optional().describe("Who can see online status"),
      last: PrivacyValueSchema.optional().describe("Who can see last seen"),
      groupadd: PrivacyValueSchema.optional().describe("Who can add to groups"),
      calladd: PrivacyValueSchema.optional().describe("Who can call"),
    };
  • Import of registerUpdatePrivacy from the update-privacy module.
    import { registerUpdatePrivacy } from "./update-privacy.js";
  • Registration call that wires up the update_privacy tool to the server and client.
    registerUpdatePrivacy(server, client);
Behavior2/5

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

With no annotations, the description carries the full burden. It states 'update' implying mutation but does not disclose side effects, immediacy of changes, or any destructive potential. Important behavioral traits are missing.

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?

The description is extremely concise: one sentence and a list. Every word serves a purpose, and the structure is front-loaded with the action and target. No wasted content.

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?

For a mutation tool with no output schema and no annotations, the description is too brief. It does not explain return values, error conditions, or behavior when parameters are omitted. The schema covers parameters, but the behavioral and contextual gaps remain.

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 baseline is 3. The description adds the list of enum values but does not explain which parameter they apply to. The schema already provides per-parameter descriptions and enum values, so the description adds marginal value.

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 action 'Update' and the target 'privacy settings for the pinned WhatsApp instance', with a specific list of allowed values. It distinguishes the tool from siblings like 'fetch_privacy' which retrieves settings.

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 is provided about when to use this tool versus alternatives (e.g., 'set_settings' for other settings, 'fetch_privacy' for reading). There is no mention of prerequisites, conditions, or when not to use it.

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