Skip to main content
Glama
billyfranklim1

mcp-evolution

Update Profile Picture

update_profile_picture

Update the profile picture of your pinned WhatsApp instance by providing a Base64 encoded image or a URL. Ensure the image is valid and accessible.

Instructions

Update the profile picture of the pinned WhatsApp instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pictureYesBase64 encoded image or URL for the profile picture

Implementation Reference

  • The async handler that sends the POST request to /chat/updateProfilePicture/:instanceName with the picture data and returns the result.
        async (args) => {
          try {
            const data = await client.post(`/chat/updateProfilePicture/${client.instanceName}`, {
              picture: args.picture,
            });
            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;
          }
        }
      );
    }
  • Zod schema defining the 'picture' input parameter (Base64 or URL, min length 1).
    const schema = {
      picture: z.string().min(1).describe("Base64 encoded image or URL for the profile picture"),
    };
  • The registerUpdateProfilePicture function that registers the tool with the MCP server under the name 'update_profile_picture'.
    export function registerUpdateProfilePicture(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "update_profile_picture",
        {
          title: "Update Profile Picture",
          description: "Update the profile picture of the pinned WhatsApp instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(`/chat/updateProfilePicture/${client.instanceName}`, {
              picture: args.picture,
            });
            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;
          }
        }
      );
  • Registration call in the central tools index that wires up update_profile_picture.
    registerUpdateProfilePicture(server, client);
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only says 'Update' without explaining effects, requirements, or limitations (e.g., image format validation, network state). Minimal 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?

Single sentence, no redundancy, directly states purpose. Every word earns its place.

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 simple tool with one parameter and no output schema, the description is minimally complete but lacks behavioral details and context about the 'pinned' instance, which is critical for 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 coverage is 100% and the description adds no extra meaning beyond the schema's parameter description. Baseline 3 applies as the schema already documents the parameter adequately.

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 resource (profile picture) with a specific target (pinned WhatsApp instance), distinguishing it from sibling tools like remove_profile_picture and fetch_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 vs alternatives, no prerequisites, and no context about the 'pinned' instance requirement. The description is silent on decision-making.

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