Skip to main content
Glama

Update project

well_update_project
Destructive

Change a project of the current workspace: its name, kind, status, dates, amount and currency, or the project it nests under.

Use this tool when the user asks to rename a project, move it to another status (for example mark a deal won or lost), change its dates or amount, or nest it under another project. Find the project_id first with well_list_projects or well_get_project.

REQUIRED: project_id. OPTIONAL (only the fields the user wants changed): name, kind, status, start_date, end_date (YYYY-MM-DD), amount (a decimal string; it needs a currency), currency, parent_project_id. Pass null to clear an optional field.

The changed project must still fit its kind, the same rules as well_create_project: a deal takes won or lost but no start_date; a cost_center, property, pipeline or pipeline_stage is only active or archived, with no dates and no amount; only a deal or a project has an amount; a project nests under a project, a cost_center under a cost_center, an ad under a campaign, a pipeline_stage under a pipeline. A kind change that would strand a sub-project fails too. Marking a deal won or lost records when it closed.

A project a connected tool synced in (synced: true) cannot be changed in Well: the next sync would overwrite the change. The call then fails; tell the user to change it in that tool.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
nameNo
amountNo
statusNo
currencyNo
end_dateNo
project_idYesThe project to change, from well_list_projects.
start_dateNo
workspace_idNoTarget 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_idNoThe 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_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict 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.
parent_project_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
projectNo
successYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools 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_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "campaign",
      -  "ad",
      -  "audience",
      -  "flow",
      -  "deal",
      -  "cost_center",
      -  "project",
      -  "property"
      -]New value: +[
      +  "campaign",
      +  "ad",
      +  "audience",
      +  "flow",
      +  "deal",
      +  "cost_center",
      +  "project",
      +  "property",
      +  "pipeline",
      +  "pipeline_stage"
      +]
    • changedOutput schema / properties / project / properties / kind / enum
      Previous value: -[
      -  "campaign",
      -  "ad",
      -  "audience",
      -  "flow",
      -  "deal",
      -  "cost_center",
      -  "project",
      -  "property"
      -]New value: +[
      +  "campaign",
      +  "ad",
      +  "audience",
      +  "flow",
      +  "deal",
      +  "cost_center",
      +  "project",
      +  "property",
      +  "pipeline",
      +  "pipeline_stage"
      +]
  2. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources