Well

Update note

well_update_note

Destructive

Change the text or the title of a note in the current workspace.

Use this tool when the user asks to change, correct or rewrite a note ("Change the note: the mockup for Monday"). Find the note_id first with well_query_records or well_get_entity. When more than one note could be the one meant, ask which one and change nothing.

REQUIRED: note_id, and body or title (or both). body replaces the whole text: send the full new text, written the way the user said it.

A note that a connected tool synced in (a meeting recorder, Notion) keeps its text from that tool: the call fails before any card and nothing changes. The person confirms the change on a card before anything is written.

Returns { success: true, note } on success, or { success: false, error } on failure.

Input Schema

Name	Required	Description
`body`	No	The note's full new text.
`title`	No	The note's new title.
`note_id`	Yes	The note to change.
`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.
`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
`note`	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.

Changed12 schema fields changedOct 28, 2026

addedOutput schema / properties / code
```
Added value: +{
+  "type": "string"
+}
```

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"
+}
```

removedOutput schema / properties / note / properties / body / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / note / properties / body / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / note / properties / company_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / note / properties / company_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / note / properties / company_name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / note / properties / company_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / note / properties / title / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / note / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```

addedOutput schema / properties / reply_lines

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed2 schema fields changedOct 22, 2026

addedOutput schema / properties / note / properties / author

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "full_name": {
+          "type": "string"
+        },
+        "person_id": {
+          "format": "uuid",
+          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+          "type": "string"
+        }
+      },
+      "required": [
+        "person_id",
+        "full_name"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / note / required

Previous value: -[
-  "note_id",
-  "title",
-  "body",
-  "company_id",
-  "company_name"
-]New value: +[
+  "note_id",
+  "title",
+  "body",
+  "company_id",
+  "company_name",
+  "author"
+]

AddedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the destructive/readOnly annotations, the description explains that body replaces the whole text, that synced notes fail before any card and leave nothing changed, and that a person confirms on a card before writing. These are important behavioral details that materially reduce the risk of an incorrect write.

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, structured, and generally efficient. It includes return-value details despite an output schema existing, which is slightly redundant but does not obscure the key guidance.

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

Completeness5/5

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

For a destructive update tool, the description covers purpose, required inputs, lookup workflow, ambiguity handling, synced-note restrictions, confirmation behavior, and failure semantics. Combined with rich schema descriptions and an output schema, it gives the agent enough context to call the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all seven parameters. The description adds useful semantics for the core edit parameters, especially that note_id is required and that body or title must be supplied, and that body replaces the whole text rather than appending.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: change the text or title of a note in the current workspace. It clearly separates whole-note text/title editing from related operations such as note lines, creating, or deleting notes.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance with an example, tells the agent to resolve note_id first via well_query_records or well_get_entity, and instructs the agent to ask rather than guess when multiple notes match.

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?