Skip to main content
Glama

save_smart_followup_config

Update smart follow-up configuration for WhatsApp automation. Only send changed fields; system automatically checks for opt-outs and negative sentiment before sending.

Instructions

Actualizar configuracion Smart Follow-up — Actualiza la configuracion de seguimiento inteligente. Solo envia los campos que quieras cambiar. El sistema verifica automaticamente que el contacto no este dado de baja (mass marketing) y no tenga sentimiento negativo antes de enviar. [mutation] (requiere confirmación: pasar confirm=true para ejecutar)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledNoEnable or disable smart follow-up
run_hourNoHour to run (0-23) in shop's timezone
lookback_hoursNoHow many hours back to look for conversations (default 24)
min_intent_levelNoMinimum intent level to follow up: 'low', 'medium', or 'high'
max_attemptsNoMaximum follow-up attempts per conversation (1-5)
retry_interval_hoursNoHours to wait between retry attempts for the same conversation
max_conversationsNoMaximum conversations to process per cron run
auto_send_enabledNoWhether to automatically send WhatsApp follow-up messages
archive_after_sendNoWhether to archive the WhatsApp chat after sending follow-up
delay_daysNoDays to wait before sending follow-up (0-7)
run_daysNoDays of the week to run (0=Sunday, 1=Monday, ..., 6=Saturday). JSON array of integers.
tracking_daysNoDays to track conversions after follow-up is sent
reset_attempts_daysNoDays after which attempt count resets for a conversation
custom_instructionsNoInstrucciones personalizadas para la IA al generar mensajes de seguimiento
followup_toneNoTono de los mensajes de seguimiento: 'friendly' (amigable), 'professional' (profesional) o 'casual'
whatsapp_session_idNoID de la sesion de WhatsApp a usar para enviar los mensajes de seguimiento
exclude_phonesNoLista de telefonos a excluir del seguimiento (maximo 200). Formato: array de strings con prefijo +
sending_window_startNoHora de inicio de la ventana de envio (0-23). null para desactivar ventana
sending_window_endNoHora de fin de la ventana de envio (0-23). null para desactivar ventana
confirmNoPasar true para confirmar la ejecución de esta acción peligrosa
Behavior4/5

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

With no annotations, the description carries the burden. It discloses mutation behavior, the confirmation requirement, and automatic checks for unsubscribed contacts and negative sentiment. However, it could mention more about side effects or validation beyond these checks.

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 two sentences plus a short tag and note. It is front-loaded with the main action and contains no unnecessary words. Every sentence adds value.

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 configuration update tool with many parameters and no output schema, the description covers the essential behavioral aspects: partial updates, auto checks, and confirmation. It lacks details about response format or prerequisites but is sufficiently complete for typical use.

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 has 100% description coverage, so the baseline is 3. The description adds overarching context (partial updates, auto checks) but does not provide additional per-parameter semantics beyond what the schema already offers.

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 uses the verb 'Actualizar' (update) and specifies the resource 'configuración de seguimiento inteligente' (smart follow-up configuration). It clearly distinguishes from siblings like get_smart_followup_config and trigger_smart_followup.

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

Usage Guidelines4/5

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

The description provides a usage hint: 'Solo envia los campos que quieras cambiar' (only send fields you want to change). It also explains automatic checks. However, it does not explicitly state when to avoid using this tool or compare it to alternatives.

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/wazionapps/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server