Skip to main content
Glama
Jem-HR
by Jem-HR

indicate_typing

Display a typing indicator in WhatsApp conversations to signal active response preparation, improving user experience during brief response delays.

Instructions

Show typing indicator to WhatsApp user.

This marks a message as read and displays a typing indicator to show the user that you are preparing a response. Best practice when it will take a few seconds to respond.

IMPORTANT NOTES:

  • Typing indicator lasts max 25 seconds or until you send a message

  • Only use if you are actually going to respond

  • Will be dismissed when you send the next message

  • Improves user experience for delayed responses

EXAMPLE: { "message_id": "wamid.HBgNMjc2NTY4NjY5MDUVAgARGBI5QTNDMEM3RjVBMzY2Q0Y4AA==" }

Args: message_id: The WhatsApp message ID to respond to (from incoming message) sender: Optional phone ID (defaults to client's phone ID)

Returns: Dictionary with success status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
message_idYes
senderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The indicate_typing tool handler function that shows a typing indicator to WhatsApp users. It takes a message_id and optional sender parameter, calls wa_client.indicate_typing(), and returns a success status dictionary. The function includes comprehensive documentation about the typing indicator's behavior (max 25 seconds, dismissed on message send, best practices).
    @mcp.tool()
    async def indicate_typing(
        message_id: str,
        *,
        sender: Optional[str] = None,
    ) -> dict:
        """
        Show typing indicator to WhatsApp user.
        
        This marks a message as read and displays a typing indicator to show
        the user that you are preparing a response. Best practice when it will
        take a few seconds to respond.
        
        IMPORTANT NOTES:
        - Typing indicator lasts max 25 seconds or until you send a message
        - Only use if you are actually going to respond  
        - Will be dismissed when you send the next message
        - Improves user experience for delayed responses
        
        EXAMPLE:
        {
          "message_id": "wamid.HBgNMjc2NTY4NjY5MDUVAgARGBI5QTNDMEM3RjVBMzY2Q0Y4AA=="
        }
        
        Args:
            message_id: The WhatsApp message ID to respond to (from incoming message)
            sender: Optional phone ID (defaults to client's phone ID)
        
        Returns:
            Dictionary with success status
        """
        try:
            result = wa_client.indicate_typing(
                message_id=message_id,
                sender=sender,
            )
            
            logger.info(f"Typing indicator shown for message {message_id}")
            # SuccessResult has a success boolean attribute
            success_status = getattr(result, 'success', bool(result))
            
            return {
                "success": True, 
                "typing_indicated": success_status,
                "message_id": message_id
            }
        except Exception as e:
            logger.error(f"Failed to indicate typing: {str(e)}")
            return {"success": False, "error": str(e)}
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the typing indicator duration (max 25 seconds), dismissal conditions (when sending next message), and the read-marking side effect. However, it doesn't mention potential errors, rate limits, or authentication requirements.

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 well-structured with clear sections (purpose, notes, example, args, returns). Every sentence adds value: the opening states the core function, the notes provide critical behavioral context, the example illustrates usage, and the parameter/return explanations are necessary given the 0% schema coverage.

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?

For a tool with no annotations, 0% schema coverage, but with an output schema, the description does well by covering purpose, usage, behavior, and parameters. The output schema handles return values, so the description appropriately focuses on input semantics and behavioral context. Minor gaps include lack of error handling details.

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 description coverage is 0%, so the description must compensate. It provides an example showing 'message_id' usage and explains that 'sender' is optional with a default. While it clarifies the purpose of 'message_id' (to respond to incoming message), it doesn't fully detail 'sender' semantics beyond the default.

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 tool's purpose with specific verbs ('show typing indicator', 'marks a message as read') and resources ('WhatsApp user'). It distinguishes from siblings like 'mark_message_as_read' by emphasizing the typing indicator display and user experience improvement for delayed responses.

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?

The description provides explicit guidance on when to use ('Best practice when it will take a few seconds to respond'), when not to use ('Only use if you are actually going to respond'), and alternatives (implied by sibling tools like 'send_message' for immediate responses). The 'IMPORTANT NOTES' section reinforces usage context.

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/Jem-HR/pywa-mcp-server'

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