Skip to main content
Glama
billyfranklim1

mcp-evolution

Update Group Subject

update_group_subject

Changes the name of a WhatsApp group using the instance's connection. Provide the group JID and new subject to update the group's display name.

Instructions

Update the name/subject of a WhatsApp group via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupJidYesGroup JID (e.g. 120363000000000000@g.us)
subjectYesNew group subject/name

Implementation Reference

  • The registerUpdateGroupSubject function registers the 'update_group_subject' tool handler. It accepts groupJid and subject, sends a POST to /group/updateGroupSubject/{instanceName}?groupJid=..., and returns the API response.
    export function registerUpdateGroupSubject(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "update_group_subject",
        {
          title: "Update Group Subject",
          description: "Update the name/subject of a WhatsApp group via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(
              `/group/updateGroupSubject/${client.instanceName}?groupJid=${encodeURIComponent(args.groupJid)}`,
              { subject: args.subject }
            );
            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 for the tool: groupJid (string) and subject (string), both required.
    const schema = {
      groupJid: z.string().min(1).describe("Group JID (e.g. 120363000000000000@g.us)"),
      subject: z.string().min(1).describe("New group subject/name"),
    };
  • Registration call: registerUpdateGroupSubject(server, client) invoked in the tools index.
    registerUpdateGroupSubject(server, client);
  • Import of registerUpdateGroupSubject from './update-group-subject.js' in the tools index.
    import { registerUpdateGroupSubject } from "./update-group-subject.js";
Behavior3/5

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

The description indicates a mutation (update), which is consistent with the action. However, without annotations, it does not disclose potential side effects, requirement for admin rights, or whether the change is immediate/retroactive.

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?

One short sentence of 12 words, no fluff. Every word earns its place.

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 simple update operation with two well-documented parameters and no output schema, the description is sufficiently complete. It could mention the expected outcome (e.g., group subject changes immediately), but the current level is adequate.

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 schema already documents both parameters. The description adds no extra meaning beyond what the schema provides, meeting the baseline of 3.

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 (name/subject of a WhatsApp group). It distinguishes from sibling tools like create_group and update_group_description by focusing specifically on the subject.

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 such as update_group_description or create_group. No mention of prerequisites like admin permissions or group membership.

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