Skip to main content
Glama
billyfranklim1

mcp-evolution

Update Group Picture

update_group_picture

Update a WhatsApp group's profile picture by providing the group JID and a base64-encoded image or image URL via the Evolution API instance.

Instructions

Update the profile picture of a WhatsApp group via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupJidYesGroup JID (e.g. 120363000000000000@g.us)
imageYesBase64 encoded image or URL for the group picture

Implementation Reference

  • The registerUpdateGroupPicture function that registers and implements the tool handler. It posts to /group/updateGroupPicture/:instance endpoint with groupJid and image parameters.
    export function registerUpdateGroupPicture(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "update_group_picture",
        {
          title: "Update Group Picture",
          description: "Update the profile picture of a WhatsApp group via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(
              `/group/updateGroupPicture/${client.instanceName}?groupJid=${encodeURIComponent(args.groupJid)}`,
              { image: args.image }
            );
            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 update_group_picture: groupJid (string) and image (base64/URL string).
    const schema = {
      groupJid: z.string().min(1).describe("Group JID (e.g. 120363000000000000@g.us)"),
      image: z.string().min(1).describe("Base64 encoded image or URL for the group picture"),
    };
  • Registration call for registerUpdateGroupPicture in the central tools index.
    registerUpdateGroupPicture(server, client);
  • Import of registerUpdateGroupPicture from the module.
    import { registerUpdateGroupPicture } from "./update-group-picture.js";
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions 'via the pinned instance' but doesn't explain what that means regarding authentication or access. No disclosure of side effects, limits, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, clear sentence with no extraneous words. Efficient but could include more useful details without becoming verbose.

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?

For a straightforward update tool with two required parameters and no output schema, the description is minimally adequate but lacks behavioral context (e.g., return value, error scenarios).

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% with descriptions for both parameters. Description adds 'Base64 encoded image or URL' which matches schema, but no extra context like size limits or format details.

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 ('profile picture of a WhatsApp group'), and is distinct from sibling tools like 'remove_profile_picture' and 'update_profile_picture'.

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., 'update_profile_picture' for user profile, or 'remove_profile_picture' to delete). No prerequisites mentioned.

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