Well

Update chat conversation

well_update_chat_conversation

Change the title or saved tabs of one conversation the current member owns. Use thread_id from the chat_conversations records. An active_tab_key must name a tab in the saved list; null clears the selection. Conversation history and routing remain service-owned.

Input Schema

Name	Required	Description
`tabs`	No
`notes`	No
`title`	No
`thread_id`	Yes
`workspace_id`	No	Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
`active_tab_key`	No
`conversation_id`	No	The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
`idempotency_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
`workspace_scope`	No	Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

Name	Required	Description
`code`	No
`data`	No
`error`	No
`success`	Yes
`reply_lines`	No
`conversation_id`	No	The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
`near_candidates`	No
`newly_connected`	No	Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
`conversation_id_note`	No	Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.
`conversation_id_source`	No	Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
`near_candidates_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 1, 2026

addedInput schema / properties / notes

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 10000,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedInput schema / properties / tabs / items / properties / destinationId / enum

Previous value: -[
-  "new_tab",
-  "workflows",
-  "tasks",
-  "graph",
-  "boards",
-  "projects",
-  "people",
-  "companies",
-  "invoices",
-  "transactions",
-  "accounts",
-  "account_balances",
-  "payment_means",
-  "supplier_payment_terms",
-  "ledger_accounts",
-  "journals",
-  "journal_entries",
-  "tax_rates",
-  "categories",
-  "documents",
-  "notes",
-  "payslips",
-  "calendar_events",
-  "emails",
-  "media",
-  "connectors",
-  "locations",
-  "web_links",
-  "phones",
-  "members",
-  "billing",
-  "settings",
-  "blueprint_runs",
-  "chat_conversations",
-  "billing_events",
-  "activities",
-  "invoice_items",
-  "invoice_payment_means",
-  "invoice_transactions",
-  "cards",
-  "checks",
-  "exchange_rates",
-  "memberships",
-  "record_workspaces",
-  "connector_install",
-  "mcp_install",
-  "record"
-]New value: +[
+  "new_tab",
+  "workflows",
+  "tasks",
+  "graph",
+  "boards",
+  "projects",
+  "people",
+  "companies",
+  "invoices",
+  "transactions",
+  "accounts",
+  "account_balances",
+  "payment_means",
+  "supplier_payment_terms",
+  "ledger_accounts",
+  "journals",
+  "journal_entries",
+  "tax_rates",
+  "categories",
+  "documents",
+  "notes",
+  "payslips",
+  "calendar_events",
+  "emails",
+  "media",
+  "connectors",
+  "locations",
+  "web_links",
+  "phones",
+  "members",
+  "billing",
+  "settings",
+  "blueprint_runs",
+  "chat_conversations",
+  "billing_events",
+  "activities",
+  "invoice_items",
+  "invoice_payment_means",
+  "invoice_transactions",
+  "cards",
+  "checks",
+  "exchange_rates",
+  "memberships",
+  "record_workspaces",
+  "connector_install",
+  "mcp_install",
+  "meeting_capture",
+  "record"
+]

addedOutput schema / properties / data / properties / attributes / properties / notes
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changed

Output schema / properties / data / properties / attributes / properties / tabs / items / properties / destinationId / enum

Previous value: -[
-  "new_tab",
-  "workflows",
-  "tasks",
-  "graph",
-  "boards",
-  "projects",
-  "people",
-  "companies",
-  "invoices",
-  "transactions",
-  "accounts",
-  "account_balances",
-  "payment_means",
-  "supplier_payment_terms",
-  "ledger_accounts",
-  "journals",
-  "journal_entries",
-  "tax_rates",
-  "categories",
-  "documents",
-  "notes",
-  "payslips",
-  "calendar_events",
-  "emails",
-  "media",
-  "connectors",
-  "locations",
-  "web_links",
-  "phones",
-  "members",
-  "billing",
-  "settings",
-  "blueprint_runs",
-  "chat_conversations",
-  "billing_events",
-  "activities",
-  "invoice_items",
-  "invoice_payment_means",
-  "invoice_transactions",
-  "cards",
-  "checks",
-  "exchange_rates",
-  "memberships",
-  "record_workspaces",
-  "connector_install",
-  "mcp_install",
-  "record"
-]New value: +[
+  "new_tab",
+  "workflows",
+  "tasks",
+  "graph",
+  "boards",
+  "projects",
+  "people",
+  "companies",
+  "invoices",
+  "transactions",
+  "accounts",
+  "account_balances",
+  "payment_means",
+  "supplier_payment_terms",
+  "ledger_accounts",
+  "journals",
+  "journal_entries",
+  "tax_rates",
+  "categories",
+  "documents",
+  "notes",
+  "payslips",
+  "calendar_events",
+  "emails",
+  "media",
+  "connectors",
+  "locations",
+  "web_links",
+  "phones",
+  "members",
+  "billing",
+  "settings",
+  "blueprint_runs",
+  "chat_conversations",
+  "billing_events",
+  "activities",
+  "invoice_items",
+  "invoice_payment_means",
+  "invoice_transactions",
+  "cards",
+  "checks",
+  "exchange_rates",
+  "memberships",
+  "record_workspaces",
+  "connector_install",
+  "mcp_install",
+  "meeting_capture",
+  "record"
+]

changedOutput schema / properties / data / properties / attributes / required

Previous value: -[
-  "title",
-  "mode",
-  "page_path",
-  "tabs",
-  "active_tab_key",
-  "total_tokens",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "title",
+  "notes",
+  "mode",
+  "page_path",
+  "tabs",
+  "active_tab_key",
+  "total_tokens",
+  "created_at",
+  "updated_at"
+]

Changed14 schema fields changedOct 28, 2026
- addedOutput schema / properties / code
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / data / properties / attributes / properties / active_tab_key / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / active_tab_key / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / attributes / properties / mode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / mode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / attributes / properties / page_path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / page_path / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / attributes / properties / title / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / attributes / properties / updated_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / updated_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / near_candidates
```
Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "company_id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "company_id",
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / near_candidates_truncated
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / reply_lines
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / tabs / items / properties / destinationId / enum

Previous value: -[
-  "new_tab",
-  "workflows",
-  "tasks",
-  "graph",
-  "boards",
-  "projects",
-  "people",
-  "companies",
-  "invoices",
-  "transactions",
-  "accounts",
-  "account_balances",
-  "payment_means",
-  "ledger_accounts",
-  "journals",
-  "journal_entries",
-  "tax_rates",
-  "categories",
-  "documents",
-  "notes",
-  "payslips",
-  "calendar_events",
-  "emails",
-  "media",
-  "connectors",
-  "locations",
-  "web_links",
-  "phones",
-  "members",
-  "billing",
-  "settings",
-  "blueprint_runs",
-  "chat_conversations",
-  "billing_events",
-  "activities",
-  "invoice_items",
-  "invoice_payment_means",
-  "invoice_transactions",
-  "cards",
-  "checks",
-  "exchange_rates",
-  "memberships",
-  "record_workspaces",
-  "connector_install",
-  "mcp_install",
-  "record"
-]New value: +[
+  "new_tab",
+  "workflows",
+  "tasks",
+  "graph",
+  "boards",
+  "projects",
+  "people",
+  "companies",
+  "invoices",
+  "transactions",
+  "accounts",
+  "account_balances",
+  "payment_means",
+  "supplier_payment_terms",
+  "ledger_accounts",
+  "journals",
+  "journal_entries",
+  "tax_rates",
+  "categories",
+  "documents",
+  "notes",
+  "payslips",
+  "calendar_events",
+  "emails",
+  "media",
+  "connectors",
+  "locations",
+  "web_links",
+  "phones",
+  "members",
+  "billing",
+  "settings",
+  "blueprint_runs",
+  "chat_conversations",
+  "billing_events",
+  "activities",
+  "invoice_items",
+  "invoice_payment_means",
+  "invoice_transactions",
+  "cards",
+  "checks",
+  "exchange_rates",
+  "memberships",
+  "record_workspaces",
+  "connector_install",
+  "mcp_install",
+  "record"
+]

changed

Output schema / properties / data / properties / attributes / properties / tabs / items / properties / destinationId / enum

Previous value: -[
-  "new_tab",
-  "workflows",
-  "tasks",
-  "graph",
-  "boards",
-  "projects",
-  "people",
-  "companies",
-  "invoices",
-  "transactions",
-  "accounts",
-  "account_balances",
-  "payment_means",
-  "ledger_accounts",
-  "journals",
-  "journal_entries",
-  "tax_rates",
-  "categories",
-  "documents",
-  "notes",
-  "payslips",
-  "calendar_events",
-  "emails",
-  "media",
-  "connectors",
-  "locations",
-  "web_links",
-  "phones",
-  "members",
-  "billing",
-  "settings",
-  "blueprint_runs",
-  "chat_conversations",
-  "billing_events",
-  "activities",
-  "invoice_items",
-  "invoice_payment_means",
-  "invoice_transactions",
-  "cards",
-  "checks",
-  "exchange_rates",
-  "memberships",
-  "record_workspaces",
-  "connector_install",
-  "mcp_install",
-  "record"
-]New value: +[
+  "new_tab",
+  "workflows",
+  "tasks",
+  "graph",
+  "boards",
+  "projects",
+  "people",
+  "companies",
+  "invoices",
+  "transactions",
+  "accounts",
+  "account_balances",
+  "payment_means",
+  "supplier_payment_terms",
+  "ledger_accounts",
+  "journals",
+  "journal_entries",
+  "tax_rates",
+  "categories",
+  "documents",
+  "notes",
+  "payslips",
+  "calendar_events",
+  "emails",
+  "media",
+  "connectors",
+  "locations",
+  "web_links",
+  "phones",
+  "members",
+  "billing",
+  "settings",
+  "blueprint_runs",
+  "chat_conversations",
+  "billing_events",
+  "activities",
+  "invoice_items",
+  "invoice_payment_means",
+  "invoice_transactions",
+  "cards",
+  "checks",
+  "exchange_rates",
+  "memberships",
+  "record_workspaces",
+  "connector_install",
+  "mcp_install",
+  "record"
+]

AddedOct 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish this is a non-read, non-destructive mutation, so the bar is lower. The description adds real context beyond them: an ownership requirement, the invariant that active_tab_key must exist in the saved tab list, and that conversation history and routing are service-owned and untouched by this call. It stops short of saying whether the `tabs` array replaces or merges with the existing list.

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?

Four short sentences, front-loaded with the operation and followed by the two most error-prone constraints. No filler. Slight inefficiency in that the opening sentence's field list is incomplete relative to the schema, which makes later sentences do correction work.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Still, for a 9-parameter mutation at 44% schema description coverage, the description leaves the `notes` parameter and the tabs replacement semantics entirely unaddressed — the two points where an agent is most likely to call this incorrectly.

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 44%, so the description has to compensate and it partly does: it explains active_tab_key's referential constraint and null-clears semantics, and where thread_id comes from — none of which the schema states. However, `notes`, `tabs` (replacement vs merge), and the interaction between workspace_id and active_tab_key are left undocumented in both places, so the coverage gap is only partially closed.

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 (Change) and the exact mutable fields (title, saved tabs) on a single conversation scoped to the current member. That is enough to distinguish it from well_create_chat_conversation and well_delete_chat_conversation. It loses a point because the schema also exposes a `notes` field that the stated purpose never mentions, so the described scope is narrower than the real one.

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?

"Use thread_id from the chat_conversations records" gives the identification source, and "the current member owns" is a precondition, so usage is implied rather than spelled out. There is no explicit statement of when to choose this over create/delete, and no note on what happens if the member does not own the conversation.

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

All Well tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?