Skip to main content
Glama

Update Entry

update_entry

Modify an existing journal entry's content, tags, type, or metadata while preserving its markdown section structure. Use it to correct details, clear fields with null, or move entries between workspaces.

Instructions

Update an existing journal entry. When updating content, preserve the existing markdown structure (## section headers). Do NOT restructure or add new top-level sections unless explicitly requested. Pass null to clear a metadata field. Supports content, type, tags, and 11 metadata fields including significance, project, issue, PR, and workflow.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
pr_urlNo
contentNoUpdated markdown content. Preserve the existing ## section header structure. For session summaries, keep the ## Accomplished / ## Unfinished / Blocked / ## Context for Next Session / ## Commits structure intact. Do NOT restructure or add new top-level sections unless explicitly requested.
entry_idNo
issue_urlNo
pr_numberNo
pr_statusNo
entry_typeNo
session_idNoAgent session ID for thread isolation.
is_archivedNo
is_personalNo
trust_scoreNoHeuristic score (0.0-1.0) indicating confidence (0.3-0.5 for unverified, 0.9+ for verified).
auto_contextNo
impact_scoreNoHeuristic score (0.0-1.0) indicating blast radius (0.9+ for core architecture, 0.1 for simple docs).
issue_numberNo
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.
project_ownerNo
workflow_nameNo
project_numberNo
workflow_run_idNo
workflow_statusNo
expected_versionNo
significance_typeNo
validation_statusNoCurrent validation status of the entry (passed, none, failed).
target_workspace_idNoTarget workspace to move entry into (e.g. "mysql-mcp")

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
entryNo
errorNoHuman-readable error message
detailsNoAdditional error context
successNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
indexStatusNo
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv9.1.0
    • changedInput schema / properties / content / description
      Previous value: -"Updated markdown content. Preserve the existing ## section header structure. For session summaries, keep the ## Accomplished / ## Unfinished / Blocked / ## Context for Next Session structure intact. Do NOT restructure or add new top-level sections unless explicitly requested."New value: +"Updated markdown content. Preserve the existing ## section header structure. For session summaries, keep the ## Accomplished / ## Unfinished / Blocked / ## Context for Next Session / ## Commits structure intact. Do NOT restructure or add new top-level sections unless explicitly requested."
    • addedInput schema / properties / target_workspace_id
      Added value: +{
      +  "description": "Target workspace to move entry into (e.g. \"mysql-mcp\")",
      +  "type": "string"
      +}
  2. First observedv9.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation, so the bar is lower; the description still adds real value by disclosing that null explicitly clears fields and that content edits must respect existing markdown structure. However, it omits key behavioral facts: whether omitted fields are left untouched (partial vs. full replace), what the expected_version parameter does on conflict, and that target_workspace_id relocates the entry between workspaces. Clearing a field with null is a mild data-loss action that sits somewhat at odds with destructiveHint=false, though it is a clarification rather than a contradiction.

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 sentences, front-loaded with the core action and the biggest footgun (content restructuring), with no filler. Minor waste: the markdown-preservation instruction duplicates the near-identical text already in the content property's schema description.

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

Completeness2/5

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

For a 25-parameter mutation tool with zero required parameters and low schema coverage, the description covers only the content-shape rule and null-clearing. It never explains entry identification, concurrency via expected_version, workspace moves, or the difference between an omitted and a null field — all decisions an agent must get right before calling. The output schema relieves it of describing return values, but the input-side gaps remain substantial.

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

Parameters2/5

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

Schema description coverage is only 28% across 25 parameters, so the description must carry meaning and largely does not. It adds one genuinely useful semantic ('pass null to clear a metadata field') and loosely names field categories, but never addresses expected_version, target_workspace_id, is_archived, is_personal, project_owner/project_number, workflow_run_id/workflow_status, or auto_context — leaving the majority of the surface undocumented in both places.

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: 'Update an existing journal entry', and enumerates the field families it can change (content, type, tags, metadata). That is enough for an agent to distinguish it from create_entry or delete_entry, but it never names a sibling such as batch_update_entries or team_update_entry, so the boundary is inferred rather than stated.

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?

Useful in-case guidance is present: preserve the '##' header structure, do not add top-level sections unless explicitly requested, and pass null to clear a metadata field. What is missing is any routing guidance — no statement of when to prefer this over batch_update_entries, team_update_entry, or restore_entry, and no stated prerequisite that an entry must be identified first even though entry_id is not marked required.

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

Deploy Server

Other Tools