Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat

whatsapp_pin_message

Pin or unpin a message in a WhatsApp chat. Provide message ID, chat ID, and sender ID. Optionally set an expiration duration (e.g., 24h, 7d) to automatically unpin after the specified time.

Instructions

Pin or unpin a message in a chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYesMessage ID
chatIdYesChat JID
senderIdYesMessage sender JID
pinnedNoTrue to pin, false to unpin
pinExpirationNoPin expiration (e.g. 24h, 7d, 30d)
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states the basic action (pin/unpin) and does not mention permissions, error handling, side effects (e.g., unpinning an already pinned message), or rate limits. This is minimal for a mutation tool.

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?

The description is a single, short sentence that delivers the core purpose with no superfluous words. It is appropriately front-loaded and easy to parse.

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?

Given no output schema and no annotations, the description fails to provide sufficient context for safe or effective use. It does not explain expected behavior in edge cases, such as invalid IDs, or clarify that pinning is typically limited to group chats (if applicable).

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?

The input schema has 100% description coverage, so all parameters are already explained. The description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

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?

The description clearly states the action ('Pin or unpin') and the resource ('a message in a chat'). It effectively distinguishes from sibling tools like 'whatsapp_pin_chat' (pinning a chat) and 'whatsapp_star_message' (starring a message).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as when to pin versus star a message, or when to pin a message versus pin a chat. It lacks any contextual or conditional advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wsapi-chat/wsapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server