whatsmcp

Set Profile Photo

wa_set_profile_photo

DestructiveIdempotent

Change the profile photo of one of your own WhatsApp accounts — the picture every contact sees. Pass image_base64 (JPEG, PNG or GIF, at most 5 MiB) to replace it: the image is center-cropped to a square and scaled to at most 640x640, as WhatsApp stores it. Or pass remove=true to delete the current photo. The previous photo cannot be restored afterwards. Contacts may keep seeing the old photo for a while until their app refreshes it.

Input Schema

TableJSON Schema

Name	Required	Description
`remove`	No	true removes the account's current profile photo instead of replacing it; image_base64 must then be omitted
`account_id`	Yes	the account whose own profile photo to change, as returned by wa_list_accounts
`image_base64`	No	the new photo: base64-encoded JPEG, PNG or GIF, at most 5 MiB decoded. It is center-cropped to a square and scaled to at most 640x640. Omit it when remove is true

Output Schema

TableJSON Schema

Name	Required	Description
`bytes`	No	the size of the JPEG that was uploaded; absent on a removal
`width`	No	the stored photo's side in pixels (it is always square); absent on a removal
`status`	Yes	ok (WhatsApp accepted the change) or refused (nothing was done)
`refusal`	No	present only when status is refused
`summary`	No	a human-readable result
`picture_id`	No	the id WhatsApp assigned the new photo; absent on a removal

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedOutput schema / properties / refusal / properties / account_status

Added value: +{
+  "description": "when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / account_status_reason

Added value: +{
+  "description": "the detail of account_status, e.g. no_egress, stopped, no_plan",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / since

Added value: +{
+  "description": "when the number stopped working, RFC3339, when known",
+  "type": "string"
+}

First observedSep 27, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that the previous photo is unrecoverable, that the image is center-cropped to a square and downscaled to 640x640 'as WhatsApp stores it', and that contacts may keep seeing the old photo until their app refreshes. This irreversibility and propagation context is exactly what destructiveHint=true alone cannot convey.

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?

Front-loads the core action, then presents the replace/remove branches, then the irreversible and propagation caveats — each sentence carries new information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with full annotation coverage, an output schema, and complete parameter docs, the description supplies everything the agent still needs: both operation modes, irreversibility, image normalization, and eventual-consistency behavior.

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 parameter contract is already documented, and the description largely restates the image_base64 constraints (formats, 5 MiB cap, crop/scale). It adds only marginal meaning (why the crop happens), so the baseline 3 is appropriate.

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?

States a precise verb+resource ('Change the profile photo') and scopes it to 'one of your own WhatsApp accounts', making it unmistakable against siblings like wa_get_profile or wa_set_presence. An agent can identify both the action and the target without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly lays out the two modes of use — pass image_base64 to replace, or remove=true to delete — with the constraint that image_base64 must be omitted when removing. It stops short of naming exclusions (e.g., other accounts, alternative tools) or prerequisite conditions such as the account being paired.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All whatsmcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?