Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

set_conversational_automation

Configure WhatsApp conversational automation by updating welcome messages, prompts, and commands to control automated chat responses through the 1msg Chat API.

Instructions

Update WhatsApp conversational components.

Allowed body fields (others are ignored):

  • enable_welcome_message (boolean)

  • prompts (string[], max 4, each ≤ 80 chars)

  • commands ({ command_name, command_description }[])

Proxies Meta/360dialog POST /conversational_automation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_conversational_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptsNo
commandsNo
enable_welcome_messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it does disclose meaningful behavior by stating that unrecognized body fields are ignored (partial-update semantics rather than error), and it names the upstream Meta/360dialog endpoint as a POST, confirming a mutation. However, it says nothing about permission requirements, whether omitted fields are preserved or reset, rate limits, or what the response contains.

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?

Three short blocks: a one-line purpose, a bulleted field reference, and the upstream endpoint. No filler, and the mutability scope is front-loaded before the detail.

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?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers inputs well but leaves gaps around side effects (does setting prompts replace the existing list?), authorization, and the absence of any success/failure signaling. Adequate to invoke, not complete enough to predict the effect.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: it documents all three parameters and adds constraints the schema lacks entirely — prompts capped at 4 items of 80 characters each, and the command object's two required keys. Format details for command_name (length, allowed characters) are still missing.

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?

'Update WhatsApp conversational components' gives a concrete verb plus resource, and the field list pins down exactly which components are mutable (welcome message, prompts, commands), so an agent knows what the tool touches. It stops short of naming the read counterpart get_conversational_automation or otherwise differentiating itself from the large sibling set.

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 field list implies when the tool applies (configuring welcome messages/prompts/commands), but there is no explicit 'use this when...' statement, no note that get_conversational_automation should be called first to inspect current state, and no prerequisites such as owning a WABA.

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