Skip to main content
Glama

Message: Resolve chat

message_resolve_chat
Read-onlyIdempotent

List/search conversations so a human recipient/topic can be mapped to exact chat_id before reading/replying or resolving message_id. Do not use a person name as chat_id. For Facebook Pages use facebook_list_inboxes and facebook_list_inbox_chats to preserve Page identity. For LinkedIn use linkedin_list_inboxes then linkedin_list_inbox_chats because account-wide chat listing is not supported. 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.

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": {
      "provider": "<provider>"
    },
    "name": "message_resolve_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
providerYes
is_unreadNo
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "whatsapp",
      -  "instagram",
      -  "telegram"
      -]New value: +[
      +  "whatsapp",
      +  "instagram",
      +  "facebook",
      +  "telegram"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful resolution semantics and identifier constraints, but it does not explain what the tool returns, how pagination/filtering works, or how items are ordered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and routing warnings are front-loaded, but there is duplication between 'Do not use a person name as chat_id' and 'Never pass: person name,' and the LinkedIn URL detail is not clearly relevant to a tool whose provider enum excludes LinkedIn.

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?

For a 5-parameter resolution tool with low schema description coverage and no output schema, the description leaves major gaps: parameter meanings, provider-specific behavior, return shape, and pagination are undocumented. It provides useful identity-resolution guidance but not enough to call the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, and the description does not explain limit, cursor, is_unread, or the provider enum. It mentions 'provider list conversations/inbox chats' only vaguely and refers to chat_id, which is not an input parameter here.

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 states a specific goal: map a human recipient or topic to an exact chat_id before reading, replying, or resolving a message_id. It is more specific than a generic chat-listing tool, though the opening phrase 'List/search conversations' overlaps with siblings like messaging_list_chats and could blur the distinction.

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

Usage Guidelines4/5

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

It gives explicit usage conditions, warnings against using person names as chat_id, and provider-specific alternatives for Facebook Pages and LinkedIn. However, the LinkedIn routing advice conflicts with the provider enum, which does not include LinkedIn, creating some confusion about when this tool itself applies.

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.