Skip to main content
Glama

Update project fields

updateProject
Idempotent

Patch project metadata (name, lifecycle status, externalRef). Pass projectId, or project with the name the user said; with neither, the result lists their projects and nothing is written. preview=true returns the field-level diff and writes nothing. A write returns a receipt; undoOperationId restores the captured prior fields. Does not archive or delete.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>"
    },
    "name": "updateProject"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
previewNoWhen true, return the field-level diff and write nothing. Combined with undoOperationId, returns the stored receipt.
projectNoProject name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.
projectIdNoProject UUID. Omit if you pass `project`.
externalRefNoProvenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Pass null to clear.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
lifecycleStatusNoProject stage. getProjectContext returns it as lifecycleStatus.
undoOperationIdNoReceipt id from a prior updateProject write. Restores the captured prior fields. With preview=true, inspects the receipt instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""New value: +"A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details."
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "preview",
      -  "context"
      -]New value: +[
      +  "context"
      +]
  4. Changed2 schema fields changed
    • addedInput schema / properties / lifecycleStatus / description
      Added value: +"Project stage. getProjectContext returns it as lifecycleStatus."
    • addedInput schema / properties / lifecycleStatus / enum
      Added value: +[
      +  "exploring",
      +  "planning_budgeting",
      +  "permits",
      +  "ready_to_build",
      +  "in_construction"
      +]
  5. Changed2 schema fields changed
    • removedInput schema / properties / llm_model
      Removed value: -{
      -  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "preview",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "preview",
      +  "context"
      +]
  6. Changed1 schema field changed
    • removedInput schema / properties / conversation_id
      Removed value: -{
      -  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      -  "type": "string"
      -}
  7. Changed4 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "preview",
      -  "context"
      -]New value: +[
      +  "preview",
      +  "context",
      +  "llm_model"
      +]
  8. Changed3 schema fields changed
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Project name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / projectId / description
      Added value: +"Project UUID. Omit if you pass `project`."
    • changedInput schema / required
      Previous value: -[
      -  "projectId",
      -  "preview",
      -  "context"
      -]New value: +[
      +  "preview",
      +  "context"
      +]
  9. Changed1 schema field changed
    • addedInput schema / properties / externalRef
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 200,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Provenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Pass null to clear."
      +}
  10. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Because annotations say readOnlyHint=false but destructiveHint=false and idempotentHint=true, the description's job is to explain how a non-destructive write actually behaves, which it does: preview=true writes nothing, a real write returns a receipt, and undoOperationId restores the captured prior fields. It also discloses the surprising fallback where missing identifiers degrade into a read that lists projects and writes nothing. That is exactly the behavioral context the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the mutation scope, then identifier resolution, then preview/write/undo behavior, then the exclusion. No filler and no restatement of the tool name or title.

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

Completeness4/5

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

For a 9-parameter mutation tool with no output schema and no annotations covering safety, the description covers the important unknowns: dry-run semantics, receipt-and-undo lifecycle, and the read fallback. The main residual gap is what a receipt or diff actually contains, which matters precisely because there is no output schema.

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 high (89%), so the baseline is 3, but the description adds cross-parameter semantics the schema states only per-field: the projectId-or-project choice and the neither-supplied outcome. It also clarifies that preview combined with undoOperationId inspects the receipt rather than performing a diff-and-write. The mutation fields themselves (name, lifecycleStatus, externalRef) are only enumerated, not elaborated beyond the schema.

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 opens with a specific verb and resource plus the exact fields touched: "Patch project metadata (name, lifecycle status, externalRef)". It also draws a boundary at the end ("Does not archive or delete"), which rules out a class of sibling operations. It does not name or contrast with plausible siblings such as saveToProject or setProjectMapListing, so an agent can't fully rule those out from this text alone.

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 concrete routing rules: pass `projectId`, or `project` with the name the user said, and if neither is supplied the tool lists projects rather than writing. It also explains when to use preview=true versus a real write, and that undoOperationId is the reversal path. It stops short of naming alternatives for adjacent needs (e.g. saving project content), so it isn't a full when/when-not/alternative guide.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.