Skip to main content
Glama
billyfranklim1

mcp-evolution

Fetch Profile Picture

fetch_profile_picture

Retrieve the URL of a WhatsApp contact's profile picture by providing their phone number or JID through the pinned instance.

Instructions

Fetch the profile picture URL of a WhatsApp contact via the pinned instance.

Input Schema

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

Implementation Reference

  • Main handler function registerFetchProfilePicture that registers the tool with the MCP server and implements the logic to fetch a profile picture via a POST to /chat/fetchProfilePictureUrl/{instanceName}.
    export function registerFetchProfilePicture(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "fetch_profile_picture",
        {
          title: "Fetch Profile Picture",
          description: "Fetch the profile picture URL of a WhatsApp contact via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(`/chat/fetchProfilePictureUrl/${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, requiring a 'number' field validated by PhoneOrJidSchema (a JID or phone number string).
    const schema = {
      number: PhoneOrJidSchema,
    };
  • Import of the registerFetchProfilePicture function from the tool module.
    import { registerFetchProfilePicture } from "./fetch-profile-picture.js";
  • Registration call that wires registerFetchProfilePicture into the MCP server during all-tools registration.
    registerFetchProfilePicture(server, client);
  • PhoneOrJidSchema used for the 'number' input parameter, accepts a JID or phone number string.
    export const PhoneOrJidSchema = z
      .string()
      .min(1)
      .describe("Recipient JID or phone number (e.g. 5511999999999 or group@g.us)");
Behavior2/5

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

No annotations exist, so the description carries full burden. It states a read operation but does not disclose potential side effects, error scenarios, rate limits, or the meaning of 'pinned instance'. Minimal behavioral disclosure.

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 extraneous words, directly conveys the tool's purpose. Efficiently structured.

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 operation, the description covers the key elements. Lacks details on return format (though 'URL' is implied) and handling of missing pictures, but overall adequate for a straightforward tool.

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 has 100% description coverage, explaining the 'number' parameter as a JID or phone number. The description adds no additional meaning beyond 'WhatsApp contact', so baseline score of 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?

The description clearly specifies the action ('Fetch'), the resource ('profile picture URL of a WhatsApp contact'), and the context ('via the pinned instance'). It distinguishes well from sibling tools like 'remove_profile_picture' or 'update_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 Guidelines3/5

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

The description provides a clear purpose but offers no guidance on when to use this tool versus alternatives, such as when the contact lacks a profile picture or how to handle the returned URL.

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