Skip to main content
Glama
billyfranklim1

mcp-evolution

Update Profile Status

update_profile_status

Change the WhatsApp profile status (about) to a new text. Set a custom status message for the profile.

Instructions

Update the 'about' status text of the pinned WhatsApp instance's profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesNew status text (about) for the WhatsApp profile

Implementation Reference

  • The main handler function `registerUpdateProfileStatus` which registers the tool 'update_profile_status' with the MCP server. It accepts a 'status' string input, makes an HTTP POST to `/chat/updateProfileStatus/${instanceName}` with the status, and returns the response.
    import { z } from "zod";
    import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
    import { McpError } from "@modelcontextprotocol/sdk/types.js";
    import type { EvolutionClient } from "../evolution-client.js";
    
    const schema = {
      status: z.string().min(1).describe("New status text (about) for the WhatsApp profile"),
    };
    
    export function registerUpdateProfileStatus(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "update_profile_status",
        {
          title: "Update Profile Status",
          description: "Update the 'about' status text of the pinned WhatsApp instance's profile.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(`/chat/updateProfileStatus/${client.instanceName}`, {
              status: args.status,
            });
            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 using Zod: requires a 'status' field (non-empty string) describing the new profile 'about' text.
    const schema = {
      status: z.string().min(1).describe("New status text (about) for the WhatsApp profile"),
    };
  • Import of `registerUpdateProfileStatus` from the update-profile-status module.
    import { registerUpdateProfileStatus } from "./update-profile-status.js";
  • Registration call: `registerUpdateProfileStatus(server, client)` is invoked to register the tool with the MCP server.
    registerUpdateProfileStatus(server, client);
Behavior2/5

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

No annotations are provided. The description does not disclose behavioral traits such as idempotency, side effects (e.g., overwritten status), authentication requirements, or rate limits. For a mutation tool, this is insufficient.

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 with precise language. No redundant words. Highly concise and front-loaded.

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

Completeness3/5

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

Given the simple nature (one parameter, no output schema), the description is adequate but could mention instance connection requirement or format constraints. Lacks behavioral details due to missing annotations.

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 coverage is 100% with a clear description for the 'status' parameter. The tool description adds context ('pinned instance', 'about') but does not add significant meaning beyond the schema. Baseline 3 applies.

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 'update' and the specific resource: 'the 'about' status text of the pinned WhatsApp instance's profile.' It distinguishes from sibling tools like update_profile_name and update_profile_picture by specifying the exact field being updated.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., update_profile_name for name changes). No context on prerequisites or conditions.

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