Skip to main content
Glama
billyfranklim1

mcp-evolution

Remove Profile Picture

remove_profile_picture

Remove the profile picture from your pinned WhatsApp instance. This action deletes the current image and resets it to default.

Instructions

Remove the profile picture of the pinned WhatsApp instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registerRemoveProfilePicture function registers the 'remove_profile_picture' tool. It calls the Evolution API DELETE /chat/removeProfilePicture/{instanceName} to remove the profile picture of the pinned WhatsApp instance.
    export function registerRemoveProfilePicture(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "remove_profile_picture",
        {
          title: "Remove Profile Picture",
          description: "Remove the profile picture of the pinned WhatsApp instance.",
          inputSchema: {},
        },
        async () => {
          try {
            const data = await client.delete(`/chat/removeProfilePicture/${client.instanceName}`);
            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. It has an empty inputSchema object, meaning no parameters are required.
    {
      title: "Remove Profile Picture",
      description: "Remove the profile picture of the pinned WhatsApp instance.",
      inputSchema: {},
  • Registration call in registerAllTools, invoking registerRemoveProfilePicture(server, client) under the Profile section.
    registerRemoveProfilePicture(server, client);
  • Import statement for the registerRemoveProfilePicture function from the remove-profile-picture module.
    import { registerRemoveProfilePicture } from "./remove-profile-picture.js";
  • The delete method on EvolutionClient used by the handler to make the HTTP DELETE request.
    async delete<T = unknown>(path: string, body?: unknown): Promise<T> {
      return this.request<T>("DELETE", 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 full burden. It discloses that the tool removes the profile picture, but it does not mention whether the action is reversible, what happens after removal (e.g., default avatar), or any required permissions.

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?

Single sentence, no filler, front-loaded with the action and resource.

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?

Given no parameters and no output schema, the description is mostly sufficient for a simple removal action. However, it could mention what happens if no profile picture is set or error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters with 100% schema description coverage. The description does not need to add parameter information. Baseline 4 is appropriate.

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 verb 'remove' and the resource 'profile picture', distinguishing it from siblings like 'update_profile_picture' and 'fetch_profile_picture'. It adds specificity by mentioning 'pinned WhatsApp instance', which clarifies scope.

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 vs alternatives, no prerequisites (e.g., must have a profile picture set), and no conditions for 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