Skip to main content
Glama
Sign In
wwebjs-mcp

wwebjs-mcp

by victor-halla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

client_setStatus

Set a custom status message for your WhatsApp account to inform contacts about your availability or current activity.

Instructions

[Client] Set the current user's status message

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>"
    },
    "name": "client_setStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoNew status message
sessionIdYesUnique identifier for the session (alphanumeric and - allowed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral disclosure burden. It only states that it 'sets' the status message, implying a mutation, but fails to mention any side effects, permission requirements, or return behavior. This is insufficient for a tool that modifies user state.

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 fully communicates the core function without any wasted words. It is appropriately sized and front-loaded with the key action.

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?

The tool is a simple setter with a well-defined schema, but the description lacks any mention of return values, error conditions, or session requirements beyond the sessionId parameter. It is adequate but leaves gaps that could affect correct invocation in edge cases.

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?

The input schema provides full coverage for both parameters, with descriptions and examples. The description itself adds no additional parameter semantics, but does not need to since the schema is already detailed. Baseline 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 states the tool's purpose: setting the current user's status message. It uses a specific verb ('set') and resource ('current user's status message'), which distinguishes it from sibling tools like client_setDisplayName or client_setProfilePicture.

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 is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or alternative tools, leaving the agent to infer usage from context.

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

Deploy Server

Other Tools