Skip to main content
Glama

Schedule a WhatsApp status

manage_status
Destructive

Schedule a post to the user's WhatsApp Status (stories) for a future date and time, or cancel a scheduled status post. The post is made later by the user's own WhatsApp on this computer; to post right now the user uses WhatsApp itself, so there is no post-now action. Only when status posts are turned on for the account; needs the "From this computer" scheduled mode and its consent in Kaption (an assistant cannot accept consent). A status is either text (max 700 characters) on a background colour (#RRGGBB) with a font (0-7), or one image (JPG/PNG/WebP) or MP4 video with an optional caption (max 1024). Images and videos need create_attachment_upload: call it with the file's name, mime and size, PUT the raw file bytes to its uploadUrl, then call manage_status schedule with attachment: { ref: attachmentRef } (one use, within an hour). The inline attachment { name, mime, dataB64 } is still accepted. Who sees it follows the user's WhatsApp status privacy setting. WhatsApp must be open on this computer at posting time: the Kaption bot and cloud templates cannot post statuses. datetime must be in the future. Each post counts as one scheduled item in the plan's scheduling quota, and the mode's limits (per hour, per day, pending) still apply; scheduling is not a delivery confirmation.

Reading status posts is list_status_posts.

Actions: schedule: { action: "schedule", datetime: "2026-10-27T09:00:00-03:00", text: "Open today 9-18", background_color: "#25D366", font: 2 } schedule (photo/video): create_attachment_upload { name: "menu.jpg", mime: "image/jpeg", size: 245760 }, PUT the bytes to its uploadUrl, then { action: "schedule", datetime: "2026-10-27T09:00:00-03:00", attachment: { ref: "" }, caption: "New menu" } cancel: { action: "cancel", 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": {
      "action": "<action>"
    },
    "name": "manage_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoStatus item ID (cancel)
fontNoText status font index 0-7 (default 0)
textNoText status (max 700 characters). Omit when posting an attachment.
actionYesschedule or cancel
captionNoCaption for an image or video status (max 1024 characters)
datetimeNoISO 8601 date-time in the future to post at (required for schedule)
attachmentNoOne image or MP4 video for a photo/video status: { ref } from create_attachment_upload (preferred), or inline { name, mime, dataB64 }
target_sessionNoSession ID for multi-account routing
background_colorNoText status background as #RRGGBB (default #7ACCA5)

Output Schema

NameRequiredDescriptionDefault
resultNoThe JSON-compatible result returned by the Kaption extension

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false) it discloses the consent barrier an assistant cannot cross, the quota cost (one scheduled item, mode limits per hour/day/pending), the caveat that scheduling is not a delivery confirmation, and that the privacy audience follows the user's WhatsApp setting. It also states the attachment ref is single-use and expires within an hour, which is behavior no structured field conveys.

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?

Front-loaded with purpose, then constraints, then a concrete Actions block with worked examples for text, media and cancel — an efficient structure for a nine-parameter tool with heavy prerequisites. The opening paragraph is dense to the point of being a run-on, packing mode, consent, formats, quotas and delivery semantics into three sentences, which costs it the top score.

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

Completeness5/5

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

Every complexity axis is covered: prerequisites, consent barrier, platform constraints, content formats, the two-step attachment upload, quota accounting and the read-path sibling. An output schema exists, so the description is right not to spend words on return values.

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 coverage is 100%, so the baseline is 3; the description still adds meaning by framing content as mutually exclusive shapes (text + background + font versus exactly one image/MP4 with caption), stating the max lengths inline, and declaring the { ref } form preferred over the inline base64 form. The only gap is target_session, which is left entirely to the schema with no cross-account guidance.

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 and resource — schedule (or cancel) a WhatsApp Status post for a future datetime — and explicitly negates the closest wrong interpretation ('to post right now the user uses WhatsApp itself, so there is no post-now action'). It also names the sibling for the read path ('Reading status posts is list_status_posts'), so an agent can distinguish it from list_status_posts, send_message and manage_scheduled_messages without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (future-dated status), when-not-to-use (no post-now; the bot and cloud templates cannot post statuses at all), and hard prerequisites: status posts enabled, the 'From this computer' scheduled mode and its consent in Kaption, and WhatsApp open on the computer at posting time. It also routes the media case to a named sibling (create_attachment_upload) with the exact follow-up steps, leaving nothing to inference.

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