Skip to main content
Glama

Messaging: Set chat state

messaging_set_chat_state
Destructive

Update supported chat state such as read/unread, archive/pin, label or mute metadata. Only send fields explicitly requested.

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": {
      "chat_id": "<chat_id>"
    },
    "name": "messaging_set_chat_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
labelNo
chat_idYesExact chat/conversation ID from the appropriate chat/inbox listing or resolver. Never pass a person name or user ID. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
pin_statusNo
muted_untilNo
read_statusNoTrue marks the chat read; false marks it unread.
archive_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds the partial-update caution, which is meaningful against a destructive hint, but omits what happens to unmentioned state, whether omitted fields are preserved, and how unsupported states per provider fail.

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?

Two short sentences, front-loaded with the resource and scope, with no filler. It is efficient, though the terseness leaves the destructive and non-idempotent behavior to be inferred rather than stated.

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?

An 8-parameter destructive, non-idempotent mutation with 38% schema coverage and no output schema needs more than two sentences: partial-update semantics, per-provider state support, and the undocumented parameters are all unaddressed. An agent could call it correctly in the simple read/unread case but is under-informed for archive/pin/mute or multi-account scenarios.

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 only 38% (chat_id, account_id, read_status documented; name, label, pin_status, muted_until, archive_status are bare). The description partially compensates by mapping the concepts to fields ('read/unread, archive/pin, label or mute'), but it does not clarify the boolean|string 'muted_until' union or what the undocumented 'name' field does.

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?

The description names a specific verb and resource ('Update supported chat state') and enumerates the state categories it touches (read/unread, archive/pin, label, mute), which lets an agent distinguish it from message_edit, chat_update, or message_mark_read. It stops short of stating which providers or which states are actually supported despite calling them 'supported'.

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?

'Only send fields explicitly requested' is a useful invocation rule about partial updates, but the description never says when to use this tool versus the sibling narrow-state tools (message_mark_read, email_mark_read, chat_update) or which states each provider supports. Usage must be inferred from the parameter names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.