Skip to main content
Glama
billyfranklim1

mcp-evolution

Update Group Description

update_group_description

Change a WhatsApp group's description via the pinned instance. Specify the group JID and new description, or clear by sending an empty string.

Instructions

Update the description of a WhatsApp group via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupJidYesGroup JID (e.g. 120363000000000000@g.us)
descriptionYesNew group description (empty string to clear)

Implementation Reference

  • Input schema for update_group_description: defines groupJid (string) and description (string) parameters using Zod.
    const schema = {
      groupJid: z.string().min(1).describe("Group JID (e.g. 120363000000000000@g.us)"),
      description: z.string().describe("New group description (empty string to clear)"),
    };
  • Handler function that registers the 'update_group_description' tool. Takes args.groupJid and args.description, POSTs to /group/updateGroupDescription/{instance} endpoint, and returns the response as JSON text.
    export function registerUpdateGroupDescription(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "update_group_description",
        {
          title: "Update Group Description",
          description: "Update the description of a WhatsApp group via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(
              `/group/updateGroupDescription/${client.instanceName}?groupJid=${encodeURIComponent(args.groupJid)}`,
              { description: args.description }
            );
            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;
          }
        }
      );
    }
  • Import of registerUpdateGroupDescription from update-group-description module.
    import { registerUpdateGroupDescription } from "./update-group-description.js";
  • Calls registerUpdateGroupDescription(server, client) to register the tool during setup.
    registerUpdateGroupDescription(server, client);
  • The EvolutionClient.post() helper method used by the handler to make the HTTP POST request.
    async post<T = unknown>(path: string, body: unknown): Promise<T> {
      return this.request<T>("POST", path, body);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'via the pinned instance' but does not explain what that means, nor does it disclose side effects, permissions, rate limits, or what happens on failure.

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?

A single, front-loaded sentence that contains no redundancy. Every word is necessary and the structure is optimal for quick comprehension.

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

Completeness3/5

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

The tool is simple with two parameters, but the description lacks information about return values (no output schema) and does not differentiate from similar sibling tools like update_group_subject. It is minimally acceptable but not fully informative.

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?

Input schema has 100% coverage and already describes both parameters (groupJid and description) clearly. The tool description adds no additional meaning beyond the schema, so a baseline score of 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?

The description clearly states the action ('Update') and the resource ('description of a WhatsApp group'), and it distinguishes itself from sibling tools like update_group_picture, update_group_subject, and update_group_setting.

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, no prerequisites (e.g., pinned instance), and no exclusions. The description only states what it does without context.

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