Skip to main content
Glama

Chat: Update

chat_update
Destructive

Update mutable metadata of an exact chat. Resolve chat_id first; do not use person/user ID. Pass only fields explicitly requested. 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": {
      "chat_id": "<chat_id>"
    },
    "name": "chat_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
labelNo
chat_idYesExact chat/conversation ID from a conversation/chat listing or resolver. A person name/user_id is NOT a chat_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_statusNo
archive_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -{}New value: +false
    • addedInput schema / properties / archive_status
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / label
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / muted_until
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / pin_status
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / read_status
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is known. The description correctly frames this as metadata mutation and warns against ID confusion, but it never explains what makes the call destructive, whether changes are reversible, or how the account_id ambiguity is resolved at runtime.

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 purpose is front-loaded and the ID warning is prominent, which is good structure. However, the Chat ID sentence block is duplicated verbatim in the schema, so a meaningful fraction of the description is redundant rather than value-adding.

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 an 8-parameter mutation tool flagged destructive with no output schema, the description leaves critical gaps: the actual meaning and format of each mutable field, and which sibling (messaging_set_chat_state vs chat_update) owns chat state changes. Only the ID-resolution problem is fully addressed.

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 25%, so the description must carry six undocumented parameters (name, label, pin_status, muted_until, read_status, archive_status) and does not. Its chat_id guidance is copied verbatim from the schema's own chat_id description, so it adds no meaning beyond the schema, and the boolean|string muted_until union is left entirely unexplained.

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?

"Update mutable metadata of an exact chat" pairs a specific verb with a specific resource and scopes it to metadata rather than messages. It is distinguishable from chat_delete and the chat participant tools, though it never names messaging_set_chat_state, which appears to overlap on pin/mute/read/archive fields.

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?

It gives one strong negative rule (resolve chat_id first, never pass person name/user_id/message_id) and a precondition (pass only explicitly requested fields). It gives no positive when-to-use guidance and no routing to alternatives, which matters because pin_status/muted_until/read_status/archive_status look like the domain of messaging_set_chat_state.

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.