Skip to main content
Glama
whatsapp-cloud-mcp

whatsapp-cloud-mcp

Get WhatsApp business profile

get_business_profile
Read-only

Retrieves the public WhatsApp business profile for your phone number, returning about, address, description, email, websites, vertical, and profile picture details.

Instructions

Fetch the public WhatsApp business profile for your phone number (about, address, description, email, websites, vertical, profile picture).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_business_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds genuinely new context beyond them: the data is 'public', it is scoped to 'your phone number' with no parameter required, and the specific fields returned are enumerated (useful because no output schema exists). It stops short of mentioning auth requirements, rate limits, or what happens when no profile is configured.

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?

A single sentence that front-loads the action and resource, with the field list compactly parenthesized at the end. Nothing is wasted and nothing essential is pushed behind preamble.

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?

For a zero-parameter read tool with no output schema, the description does the heavy lifting by enumerating the returned fields. The only meaningful gap is error/empty-state behavior and any prerequisite account setup, which the annotations do not cover.

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 tool takes zero parameters, so the baseline is 4. The description correctly reinforces this by explaining the implicit scope ('for your phone number'), making clear the caller supplies nothing.

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?

Specific verb ('Fetch') plus specific resource ('public WhatsApp business profile') and scope ('for your phone number'). The returned field list in parentheses further pins down exactly what is retrieved, and the read-one-profile nature is unmistakable against siblings that are all send/list/upload operations.

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 only implied: an agent can infer this is the way to read profile data, and no sibling offers a competing profile-read. However, the description never states when to call it (e.g., before composing messages) or any precondition such as needing a configured business account, so guidance is implicit rather than stated.

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