Skip to main content
Glama
Sign In
wwebjs-mcp

wwebjs-mcp

by victor-halla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

session_restart

Restart a WhatsApp Web session by providing its session ID to recover from errors or refresh the connection.

Instructions

[Session] Restart session. Restarts the session with the given session ID.

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": "session_restart"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden for behavioral disclosure. It simply says 'restarts' without explaining side effects (e.g., disconnection, state reset), permissions, or whether the session ID must belong to a running session. This is insufficient for a potentially disruptive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact at two sentences, but the first sentence ('[Session] Restart session.') is redundant with the tool name and category. The second sentence adds marginal clarity. It is concise but not highly informative, earning a middle score.

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

Completeness2/5

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

Given the tool's simplicity (one parameter, no output schema, no annotations), the description still leaves crucial gaps: it does not clarify what 'restart' entails operationally, when it should be used, or its impact on ongoing sessions. This is especially important for a session-control 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?

The input schema already documents sessionId with a description and example, so schema coverage is 100%. The description's phrase 'with the given session ID' adds no extra meaning beyond the schema, leaving the baseline score at 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the action (restart) and the resource (session), and indicates it uses the provided session ID. It is unambiguous and distinct from sibling operations like session_start or session_stop, though it does not explicitly contrast with them.

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 usage context is provided. The description does not mention when to use restart versus alternatives, nor does it state prerequisites such as whether the session must already be active or what happens to active connections.

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