Skip to main content
Glama

manage_whatsapp_status

Comprehensive WhatsApp status management tool supporting all status operations. Perfect for managing status lifecycle, publishing immediate or scheduled content, and retrieving status history. Supports all WhatsApp status operations through a unified action-based interface.

Available actions:

  • get: Search and retrieve status history with comprehensive filtering

  • publish: Publish immediate status updates with text, images, or videos

  • schedule: Schedule status updates for future publishing with advanced timing

Input Schema

NameRequiredDescriptionDefault
ackNoFilter by delivery status (for get action)
widNoFilter by specific WhatsApp message IDs (for get action)
chatNoFilter status by specific chat WhatsApp ID (for get action)
flowNoFilter by message direction (for get action)
fontNoFont style for text status (for publish/schedule actions)
mineNoReturn only status published by your own WhatsApp number (for get action)
pageNoPage number for pagination (for get action)
typeNoFilter by status content types (for get action)
colorNoBackground color for text status (for publish/schedule actions)
delayNoDelay in seconds (for schedule action with scheduleType: delay)
limitNoMaximum number of status entries to retrieve (for get action)
mediaNoMedia content (image/video) for status update (for publish/schedule actions)
orderNoEnforce strict publication order for scheduled status (for publish action)
phoneNoFilter status from specific phone number or WhatsApp ID (for get action)
actionYesAction to perform on WhatsApp status
deviceNoWhatsApp device ID (24-character hex string)
searchNoSearch status by text content, contact name, or media filename (for get action)
toDateNoGet status published up to this date (for get action)
delayToNoTime notation delay (for schedule action with scheduleType: delayTo)
messageNoText content for status update (required for text status in publish/schedule actions)
fromDateNoGet status published from this date onwards (for get action)
scheduleNoSchedule options for delayed publishing (for publish action)
timezoneNoTimezone for date scheduling (for schedule action)
referenceNoFilter by custom reference field or set reference for publish/schedule
scheduledNoReturn only scheduled status to be published in the future (for get action)
sortOrderNoSort order by creation date (for get action)
publishDateNoSpecific publish date and time (for schedule action with scheduleType: date)
strictOrderNoEnforce strict publication order (for schedule action)
scheduleTypeNoType of scheduling method (required for schedule action)
idempotencyKeyNoUnique key to prevent duplicate status publishing (for publish action)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It names write-like actions but does not state permissions, visibility, reversibility, rate limits, error behavior, or side effects of publishing/scheduling status updates.

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

Conciseness4/5

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

The description is reasonably compact and uses an action-based bullet structure that is easy to scan. It has some redundancy in repeatedly emphasizing comprehensive/all status operations, but it remains front-loaded and understandable.

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?

For a 30-parameter tool with nested objects, no annotations, and no output schema, the description is under-specified. It does not explain action-specific requirements such as which parameters are needed for publish versus schedule, nor does it describe return values, permissions, or scheduling constraints.

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 parameter meanings are already well documented in the schema. The description adds only high-level action groupings and does not meaningfully clarify the 30 parameters beyond what the schema provides.

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 identifies WhatsApp status management and enumerates the three supported actions (get, publish, schedule), which makes the tool's scope understandable. It does not explicitly differentiate itself from sibling tools, but no sibling appears to cover status operations directly.

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 action list implies when each mode is appropriate: get for history retrieval, publish for immediate updates, schedule for future publishing. However, there is no explicit guidance on when to use this tool versus related siblings such as send_whatsapp_message, nor are there exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources