Skip to main content
Glama
billyfranklim1

mcp-evolution

Fetch Business Profile

fetch_business_profile

Retrieve WhatsApp Business profile details for a contact by providing their phone number or JID.

Instructions

Fetch the WhatsApp Business profile information of a contact via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesRecipient JID or phone number (e.g. 5511999999999 or group@g.us)

Implementation Reference

  • The handler function that registers and implements the 'fetch_business_profile' tool. It makes a POST request to /chat/fetchBusinessProfile/{instanceName} with the provided number and returns the business profile data as JSON.
    export function registerFetchBusinessProfile(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "fetch_business_profile",
        {
          title: "Fetch Business Profile",
          description: "Fetch the WhatsApp Business profile information of a contact via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(`/chat/fetchBusinessProfile/${client.instanceName}`, {
              number: args.number,
            });
            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: expects a 'number' field validated by PhoneOrJidSchema (a non-empty string for a JID or phone number).
    const schema = {
      number: PhoneOrJidSchema,
    };
  • Import statement for registerFetchBusinessProfile from the fetch-business-profile module.
    import { registerFetchBusinessProfile } from "./fetch-business-profile.js";
  • Registration call that wires the fetch_business_profile tool into the server.
    registerFetchBusinessProfile(server, client);
  • The PhoneOrJidSchema reused by fetch_business_profile's input schema. Accepts a JID or a phone number string.
    export const PhoneOrJidSchema = z
      .string()
      .min(1)
      .describe("Recipient JID or phone number (e.g. 5511999999999 or group@g.us)");
Behavior3/5

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

No annotations are present, so the description must convey behavioral traits. It indicates a read operation but does not disclose error handling, rate limits, or what happens if the number lacks a business profile. Adequate but not detailed.

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?

The description is a single, concise sentence that efficiently communicates the tool's purpose. No unnecessary words.

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 simple fetch tool with one parameter and no output schema, the description is fairly complete. It explains what it does and how via the pinned instance. It could mention return format, but not required when output schema is missing.

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 schema covers the parameter 'number' with a good description, and the tool description adds 'via the pinned instance', providing extra context beyond the schema. With 100% schema coverage, this is above baseline.

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 verb 'Fetch' and the resource 'WhatsApp Business profile information of a contact'. It is specific and distinct from sibling tools like 'fetch_profile_picture' or 'check_number'.

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?

The phrase 'via the pinned instance' gives some context, but there is no explicit guidance on when to use this tool vs. alternatives (e.g., check_number or get_chat_history), nor any prerequisites or limitations.

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