Skip to main content
Glama

Mark a conversation as read

mark_conversation_read
Idempotent

Marks a private conversation as read so the contact sees read receipts, such as blue ticks on WhatsApp or "Seen" on Messenger and Instagram.

Instructions

Tell the social network that the user has read a private conversation. THE CONTACT SEES IT: blue ticks on WhatsApp, "Seen" on Messenger and Instagram. Reading with list_messages does not do this, and send_message does it on its own, so only call this when the user has actually seen the conversation and wants the contact to know. network_read false means the network has no read receipts, refused (try again later) or, on WhatsApp, the last message is over 30 days old.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id_account": "<id_account>",
      "id_contact": "<id_contact>"
    },
    "name": "mark_conversation_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_accountYes
id_contactYesThe contact_id from list_conversations.
id_organizationNoThe PlanVortex organization id. Optional.

Output Schema

NameRequiredDescriptionDefault
network_readYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, but say nothing about third-party visibility; the description fills that gap by spelling out the contact-visible effect (blue ticks, 'Seen') and the failure semantics of network_read false. The only shortfall is that it never states which account/permissions the call runs under, which matters for an open-world write.

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-loads the action, then the consequence, then the routing guidance — a logical order. The final sentence is dense and reads as a compressed enumeration of failure cases, but every clause carries information.

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, yet the description still explains what network_read=false means, which is genuinely additive rather than redundant. Visibility, alternatives, and failure modes are all covered; only the account/organization scoping of the mutation is left unaddressed.

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 coverage is 67% and the description adds no meaning for id_account, id_contact, or id_organization beyond the schema. With coverage above half, the baseline of 3 is appropriate, but it does not compensate for the undocumented id_account.

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?

States a specific verb and resource: telling the social network that the user has read a private conversation. It immediately distinguishes itself from list_messages (which does not trigger receipts) and send_message (which does so implicitly), so an agent can pick it out of the sibling list without opening a schema.

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?

Gives an explicit when-to-call condition ('only call this when the user has actually seen the conversation and wants the contact to know') and names two alternatives with the reason they are not substitutes. The exclusion is as clear as the inclusion.

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