Nilyo

Chat: Update

chat_update

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.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`label`	No
`chat_id`	Yes	Exact 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_id`	No	Optional 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_status`	No
`muted_until`	No
`read_status`	No
`archive_status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 4, 2026
- 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"
+}
```
First observedSep 18, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful ID-handling constraints ('Never pass: person name, user_id, message_id'), but it does not explain what happens when fields like pin_status or archive_status change, nor any permission or reversibility details.

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?

The description is front-loaded with the purpose and then gives ID guidance in a compact, structured way. Some of the chat_id text duplicates the schema, but overall it is appropriately sized and every sentence is relevant to correct invocation.

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?

There is no output schema, and the description does not explain the semantics of six of the eight parameters, including the string or boolean forms for muted_until. It covers chat_id acquisition and negative ID constraints well but leaves significant gaps for a mutation tool with many metadata fields.

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 compensate for six undocumented parameters. Instead, it repeats the chat_id guidance that already appears in the schema and adds no meaning for name, label, pin_status, muted_until, read_status, or archive_status. An agent gets no help understanding what values those fields expect or represent.

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 verb and resource: 'Update mutable metadata of an exact chat.' It clearly distinguishes the operation from deletion or participant management, though it does not explicitly name any sibling tool. The purpose is clear enough for an agent to know this is a metadata mutation.

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 strong ID-resolution guidance: 'Resolve chat_id first; do not use person/user ID' and 'Pass only fields explicitly requested.' It also explains how to obtain the chat ID. However, it does not mention when to use this tool instead of overlapping siblings such as messaging_set_chat_state for chat state changes.

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

All Nilyo tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Chat: Update

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources