Skip to main content
Glama
luiso2

Evolution API WhatsApp MCP Server

by luiso2

read_message

Mark WhatsApp messages as read to maintain organized conversations and clear message status indicators in business messaging workflows.

Instructions

Mark message as read

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromMeNoIs message from me
idNoMessage ID
instanceNameYesInstance name
remoteJidYesChat JID

Implementation Reference

  • src/index.ts:427-439 (registration)
    Registration of the 'read_message' tool in the MCP tools array, including name, description, and input schema.
      name: 'read_message',
      description: 'Mark message as read',
      inputSchema: {
        type: 'object',
        properties: {
          instanceName: { type: 'string', description: 'Instance name' },
          remoteJid: { type: 'string', description: 'Chat JID' },
          fromMe: { type: 'boolean', description: 'Is message from me' },
          id: { type: 'string', description: 'Message ID' }
        },
        required: ['instanceName', 'remoteJid']
      }
    }
  • MCP handler for 'read_message' tool that calls the EvolutionAPI service and formats the response.
    private async handleReadMessage(args: any) {
      const result = await evolutionAPI.readMessage(args.instanceName, {
        remoteJid: args.remoteJid,
        fromMe: args.fromMe,
        id: args.id
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }
        ]
      };
    }
  • Helper method in EvolutionAPI service that makes the HTTP POST request to mark a message as read in the underlying Evolution API.
    async readMessage(instanceName: string, data: {
      remoteJid: string;
      fromMe?: boolean;
      id?: string;
    }): Promise<any> {
      const response = await this.client.post(`/chat/readMessage/${instanceName}`, data);
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Mark message as read' implies a mutation (changing message status), but it doesn't disclose behavioral traits like required permissions, whether this action is reversible, rate limits, or what happens on success/failure. The description is minimal and lacks crucial context 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, efficient sentence with zero waste. It's front-loaded with the core action ('Mark message as read'), making it easy to parse. Every word earns its place, and there's no unnecessary elaboration.

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 the tool's complexity (a mutation with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, error conditions, or return values, leaving significant gaps for an AI agent to understand how to invoke it correctly.

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?

Schema description coverage is 100%, so the schema fully documents all 4 parameters. The description adds no meaning beyond the schema—it doesn't explain parameter relationships (e.g., how 'id' relates to 'remoteJid') or usage context. Baseline 3 is appropriate as the schema handles parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Mark message as read' clearly states the action (mark as read) and resource (message), but it's vague about scope and doesn't differentiate from siblings like 'get_messages' or 'send_text'. It specifies what the tool does without being tautological, but lacks detail about what 'read' means in this context.

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. It doesn't mention prerequisites (e.g., needing a message ID), exclusions, or relationships to sibling tools like 'get_messages' (which might retrieve messages before marking them as read). Usage is implied but not explicitly stated.

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/luiso2/mcp-evolution-api'

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