Skip to main content
Glama

waha_delete_group_picture

Delete a WhatsApp group's profile picture by providing the group ID. This tool removes the current image displayed for the group.

Instructions

Remove group profile picture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesGroup ID (format: number@g.us)

Implementation Reference

  • src/index.ts:603-614 (registration)
    Tool registration including name, description, and input schema definition in the ListToolsRequestSchema handler.
    name: "waha_delete_group_picture",
    description: "Remove group profile picture.",
    inputSchema: {
      type: "object",
      properties: {
        groupId: {
          type: "string",
          description: "Group ID (format: number@g.us)",
        },
      },
      required: ["groupId"],
    },
  • Primary MCP tool handler: validates groupId parameter, calls WAHAClient.deleteGroupPicture(), and returns formatted success response.
    private async handleDeleteGroupPicture(args: any) {
      const groupId = args.groupId;
    
      if (!groupId) {
        throw new Error("groupId is required");
      }
    
      await this.wahaClient.deleteGroupPicture(groupId);
    
      return {
        content: [
          {
            type: "text",
            text: `Successfully deleted picture for group ${groupId}.`,
          },
        ],
      };
    }
  • Underlying WAHAClient helper method that performs the actual HTTP DELETE request to remove the group picture from WAHA API.
    async deleteGroupPicture(groupId: string): Promise<void> {
      if (!groupId) {
        throw new WAHAError("groupId is required");
      }
    
      const endpoint = `/api/${this.session}/groups/${encodeURIComponent(groupId)}/picture`;
    
      await this.request<void>(endpoint, {
        method: "DELETE",
      });
    }
  • src/index.ts:1100-1100 (registration)
    Handler dispatch registration in the CallToolRequestSchema switch statement that routes tool calls to the specific handler.
    return await this.handleDeleteGroupPicture(args);
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 of behavioral disclosure. 'Remove' implies a destructive mutation, but it doesn't specify whether this requires admin permissions, if the action is reversible, what error conditions might occur, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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?

Given this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks crucial context like permission requirements, side effects, error handling, or response format. For a tool that modifies group state, more behavioral details are needed to ensure safe and correct usage.

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%, with the single parameter 'groupId' documented as 'Group ID (format: number@g.us)'. The description doesn't add any parameter-specific information beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Remove') and resource ('group profile picture'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'waha_set_group_picture' (which sets the picture) and 'waha_get_group_picture' (which retrieves it). However, it doesn't explicitly mention that this is a WhatsApp-related operation, though the 'waha_' prefix provides some context.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing admin permissions), when deletion is appropriate, or what happens after removal (e.g., reverts to default). With sibling tools like 'waha_set_group_picture' available, explicit differentiation would be helpful.

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/seejux/waha-whatsapp-mcp'

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