WhatsMCP: MCP for WhatsApp

Get Profile

wa_get_profile

Read-only

Look up who a phone number is on WhatsApp, from one of your accounts: whether it is registered, its public name, about text, profile picture and — for a business — its categories, contact details and hours. An empty about or picture means the peer has not shared it with this account, not that it has none.

Input Schema

Name	Required	Description	Default
`phone`	No	the number to look up, in international form (e.g. +447700900111)
`account_id`	No	which of your accounts to ask from, from wa_list_accounts; omit it when the workspace has only one account

Output Schema

Name	Required	Description
`jid`	No
`name`	No	the best available public name
`note`	No
`about`	No	the peer's status text, when they let this account see it
`phone`	No
`refusal`	No	present only when the request was declined
`business`	No	present only for a business account
`is_business`	No	true or false when known; ABSENT means the lookup could not establish it (see note) — absence is not a no
`name_source`	No	business or none — a verified business name is vouched for by WhatsApp; "none" means nothing public is published
`on_whatsapp`	Yes	false means the number is not registered on WhatsApp at all
`picture_url`	No	a WhatsApp-hosted URL that expires; fetch it promptly

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / account_id / description

Previous value: -"which of your accounts to ask from, from wa_list_accounts"New value: +"which of your accounts to ask from, from wa_list_accounts; omit it when the workspace has only one account"

removedInput schema / required
```
Removed value: -[
-  "account_id"
-]
```

addedOutput schema / properties / refusal / properties / candidates

Added value: +{
+  "description": "on an account_ambiguous refusal: the accounts to choose from — retry with one of these as account_id",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account_id": {
+        "description": "the id to retry with as account_id",
+        "type": "string"
+      },
+      "name": {
+        "description": "the account's WhatsApp display name",
+        "type": "string"
+      },
+      "phone": {
+        "description": "the account's phone number, E.164",
+        "type": "string"
+      },
+      "status": {
+        "description": "whether the number works right now — live, connecting, or why not, as wa_list_accounts reports it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account_id"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed3 schema fields changedOct 11, 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 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results are scoped to the querying account, and an empty about/picture reflects non-sharing rather than absence of data — a real interpretation pitfall it preempts. It does not address the idempotentHint=false nuance, which is a small remaining gap.

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?

Two sentences, front-loaded with the purpose and return fields, followed by the one caveat that actually changes interpretation. No wasted text.

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?

An output schema exists so return structure needn't be explained, and the description covers the account-scoping and partial-data caveats. Adequate for a 2-parameter read tool; only the non-idempotent read behavior is left unexplained.

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%, including the international phone format example and the wa_list_accounts provenance for account_id, so the schema does the heavy lifting. The description reinforces account scoping ('from one of your accounts') but adds no format or default details beyond the schema.

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 specific verb and resource ('Look up who a phone number is on WhatsApp') and enumerates exactly what is returned: registration status, public name, about, picture, and for businesses categories/contact/hours. This is clearly a single-peer lookup, distinct from sibling list tools like wa_list_contacts or wa_get_chat.

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

Usage Guidelines3/5

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

Usage is implied by the phrasing 'from one of your accounts' and the reference to picking an account, but there is no explicit when-to-use vs when-not guidance and no sibling tool is named as an alternative (e.g., wa_get_chat for known contacts).

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

All WhatsMCP: MCP for WhatsApp 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?