Skip to main content
Glama
wuapidev

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Post a story

post_story

Publish a WhatsApp story using text on a colored background or media from a URL or uploaded file, with an optional caption.

Instructions

Post a story from the account: text on a colored background, or an image or video with an optional caption, from a public URL (mediaUrl) or a file uploaded with upload_file (uploadId).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoThe story text (required for `text`), or the caption.
typeNoDefault `text`.
mediaUrlNoImage or video: public http(s) URL of the file.
uploadIdNoThe id of an upload made with upload_file (or `POST /v1/uploads`): a file wuapi already stores. Usable for 24 hours, any number of times.
accountIdYesThe wuapi account id of the linked number to act as (from list_accounts).
idempotencyKeyNoOptional. Reuse the same key when retrying this exact call: within 24 hours wuapi returns the first result instead of doing it twice.
backgroundColorNoText stories: `#RRGGBB`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / uploadId
      Added value: +{
+  "description": "The id of an upload made with upload_file (or `POST /v1/uploads`): a file wuapi already stores. Usable for 24 hours, any number of times.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds that the post acts 'from the account' and that media must come from a public URL or an existing upload, which is modest context. It says nothing about visibility duration, audience, rate limits, or failure behavior, so it remains thin beyond what the annotations carry.

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?

A single front-loaded sentence that leads with the action and then enumerates the variants and sources; there is no filler or redundancy. Parentheticals are used to reference the parameter names rather than prose duplication.

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?

With 7 parameters fully documented in the schema and no output schema to explain, the description covers the essential decision surface: which modes exist and where media can come from. It could still be more complete about the resulting story's lifecycle and any permission requirements, but nothing critical for invoking the call 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 the baseline is 3. The description goes beyond the per-field schema text by explaining the conditional relationship between parameters: 'text' stories use text plus a colored background, while image/video stories use mediaUrl or uploadId with text acting as an optional caption. That combination logic is genuine added meaning.

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?

States a specific verb and resource ('Post a story') and enumerates the supported story variants: text on a colored background, or image/video with an optional caption. It does not explicitly contrast itself with the nearest siblings (send_text, send_media, reply_to_message), so the line between a story and a message is left implicit.

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 description implies when each parameter path applies (public URL vs. a file uploaded via upload_file) and names upload_file as a prerequisite for that path. However, it gives no explicit guidance on when to choose mediaUrl over uploadId, nor any when-not-to-use or alternative-tool routing.

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

Deploy Server

Other Tools