Skip to main content
Glama

dialogbrain

by com.dialogbrain
OverviewDiscussionsAdmin

threads_update

✏️ Update a conversation thread: rename it, add notes/description, move it to a folder, or take it out of sync.

When to use:

  • User wants to rename a chat or group

  • User wants to add notes/context about a conversation

  • User wants to organize threads into folders

  • User wants a chat to stop showing up and stop syncing (synced=false) — e.g. the personal chats on an account that is only in the workspace for its work groups. Nothing is deleted; synced=true brings it back.

For DM threads, renaming also updates the linked contact's display name by default. Pass thread_id for one thread, or thread_ids to apply the same change to several. Ids come from threads.list / search.threads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew title for the thread (max 255 chars). For a DM this ALSO renames the linked contact, so an empty string is ignored, not applied — omit the parameter when you are not renaming.
syncedNofalse takes the chat out of sync: it disappears from the inbox, from knowledge/RAG search, and the sync service stops fetching it. Messages already stored are kept and nothing is deleted. true puts it back, including a chat sync left out by itself (e.g. a large group), and queues its recent history (not on an account that syncs only new messages). The decision survives later syncs. OMIT to leave sync as it is.
folder_idNoMove thread to this folder (null removes from folder)
thread_idNoThread ID from threads.list. Use this OR thread_ids.
thread_idsNoSeveral thread IDs to apply the same change to, e.g. taking a batch of personal chats out of sync in one call. Use this OR thread_id.
descriptionNoAI context / notes for this thread. Empty string clears description.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
update_contactNoFor DM threads, also rename the linked contact (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / synced / description
      Previous value: -"false takes the chat out of sync: it disappears from the inbox, from knowledge/RAG search, and the sync service stops fetching it. Messages already stored are kept and nothing is deleted. true puts it back. The decision survives later syncs. OMIT to leave sync as it is."New value: +"false takes the chat out of sync: it disappears from the inbox, from knowledge/RAG search, and the sync service stops fetching it. Messages already stored are kept and nothing is deleted. true puts it back, including a chat sync left out by itself (e.g. a large group), and queues its recent history (not on an account that syncs only new messages). The decision survives later syncs. OMIT to leave sync as it is."
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnly=false and destructive=false, and the description explains the sync semantics that matter: nothing is deleted, stored messages are kept, the decision survives later syncs, and synced=true queues recent history except on new-messages-only accounts. The DM side effect (renaming also renames the linked contact) is a valuable non-obvious behavior. It does not describe the response shape or per-call validation failures, but that is minor.

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?

Front-loaded with the verb+resource, then structured bullets and a closing id-source note. Slight redundancy between the parenthetical DM/sync explanations and the schema descriptions, but every sentence carries information an agent needs.

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 an 8-parameter, zero-required mutation tool with no output schema, the description covers all capabilities, the DM side effect, the sync lifecycle, id sourcing, and the workspace override. Nothing an agent needs to call it correctly is missing.

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 baseline is 3; the description adds real meaning by explaining that default DM renaming updates the contact and that the two id parameters are alternatives. It largely mirrors schema detail (e.g. folder_id null removal) rather than adding syntax, so it lands just above baseline.

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?

States a specific verb (update) and resource (conversation thread) and enumerates the exact mutations: rename, add notes/description, move to folder, toggle sync. It is clearly distinguishable from siblings like threads_delete and search_threads, which perform different operations on the same resource.

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?

Explicit 'When to use' bullets cover each capability, plus a concrete example of the synced=false case (personal chats on a work-only account). It also states the thread_id vs thread_ids alternative and where ids come from (threads.list / search.threads), leaving nothing to inference.

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

All dialogbrain toolsInspect
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