Kaption WhatsApp

List scheduled messages

list_scheduled_messages

Read-onlyIdempotent

List scheduled WhatsApp messages of both modes; each item says its mode: bot - sent from Kaption's WhatsApp number, stored in Kaption's cloud local - "From this computer": sent from the user's own WhatsApp number while this computer and WhatsApp are open

Examples: Waiting to be sent: {} Only local ones, any state: { mode: "local", filter: "all" }

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": "list_scheduled_messages"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Only this mode; omit to list both
`filter`	No	Default: "pending" (not sent yet; in local mode also missed or failed ones waiting for the user)
`target_session`	No	Session ID for multi-account routing

Output Schema

Name	Required	Description	Default
`result`	No	The JSON-compatible result returned by the Kaption extension

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real operational context beyond that: local-mode messages only send while the computer and WhatsApp are open, and 'pending' in local mode also includes missed/failed items awaiting the user. It omits pagination/ordering behavior, which keeps it below a 5.

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 the purpose and mode semantics, then examples. The mode definitions are slightly verbose but each carries genuine meaning; nothing is redundant 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?

An output schema exists, so return-value detail is unnecessary, and the description's note that each item reports its mode usefully bridges it. With all parameters documented and annotations covering safety, the definition is complete enough to call correctly; only cross-tool routing guidance is missing.

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 baseline is 3; the description earns above that by explaining what 'bot' and 'local' actually mean and by demonstrating filter usage in an example, which the enum text alone does not convey. 'target_session' is left entirely to the schema.

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?

Starts with a specific verb+resource ('List scheduled WhatsApp messages') and immediately scopes it to both modes, then defines each mode ('bot' vs 'local') so an agent can distinguish this from get_scheduled_message (singular) and manage_scheduled_messages (mutation). The mode taxonomy is domain knowledge an agent cannot get from the name alone.

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 two worked examples ('{}' for waiting to be sent; '{ mode: "local", filter: "all" }' for local-only any state) give concrete invocation contexts, which is stronger than generic guidance. It does not explicitly say when to prefer get_scheduled_message or manage_scheduled_messages, so routing to siblings is left implicit.

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

All Kaption WhatsApp 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?