Sautikit

update_whatsapp_call_settings

Idempotent

Write a number's WhatsApp call settings to Meta (call hours, call-icon visibility, callback permission, voicemail) and persist them. Synchronous — unlike enable/rotate this returns only once Meta accepts the write. The write never touches the SIP block, so it cannot disturb the provisioned trunk.

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": {
      "number_id": "<number_id>",
      "settings": "<settings>"
    },
    "name": "update_whatsapp_call_settings"
  }
}

Input Schema

Name	Required	Description
`purpose`	No	Required on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
`settings`	Yes	Meta call-settings object: status, call_icon_visibility, call_icons.restrict_to_user_countries, call_hours (status/timezone_id/weekly_operating_hours/holiday_schedule), callback_permission_status, voicemail, audio_additional_codecs. Omitted fields are left unchanged at Meta. Never includes the SIP block, so this cannot disturb provisioning
`number_id`	Yes	tenant number UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds real context beyond them: the call is synchronous and returns only once Meta accepts the write (unlike enable/rotate), and the write never touches the SIP block so the provisioned trunk is safe. That is precisely the kind of blast-radius information an agent needs before a mutation. It stops short of describing failure behavior or what a rejected write looks like.

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 tight sentences, front-loaded with the action and target, then the timing contract, then the safety guarantee. Every clause carries information an agent would otherwise have to guess; nothing is padding.

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 mutation tool with no output schema and a nested settings object, the description covers the essentials: what is written, that it is synchronous, that omitted fields are preserved (reinforced by the schema), and that SIP provisioning is untouched. Missing only error/failure semantics and any precondition about the number already having WhatsApp calling enabled.

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 description coverage is 100%, so the schema already documents number_id, settings and the nested Meta call-settings object in detail. The description's field list restates what the schema says rather than adding format or constraint detail beyond it, so the 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?

States a specific verb (write and persist) against a specific resource (a number's WhatsApp call settings), and enumerates the concrete fields covered: call hours, call-icon visibility, callback permission, voicemail. The write-vs-read distinction from get_whatsapp_call_settings is implicit in 'write ... to Meta' but the scope is unmistakable.

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?

Usage is implied rather than stated: an agent can infer this is the tool for changing existing call settings, and the 'unlike enable/rotate' clause distinguishes it from those siblings on timing semantics. However, there is no explicit when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. calling must already be enabled), and no pointer to get_whatsapp_call_settings for reading current values.

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

All Sautikit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?