Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_entry

Edit an existing timeline entry by providing its ID and the fields to change. Only supplied fields are updated, preserving other values. Use it to correct or extend a previously added note.

Instructions

Edit an existing timeline entry — typically a note. Provide the entry id plus the fields you want to change (content, subject). Only the fields you supply are modified; other fields keep their current values. Cannot change the entry's type. Use this to correct or extend a note added previously.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEntry ID to update
contentNoNew body text for the entry. For notes, this is the markdown content; for emails, the body. Provide only if you want to change it.
subjectNoNew subject line. Mostly meaningful on email-type entries; on plain notes Capsule accepts the call (HTTP 200) but **does not store the subject and does not advance `updatedAt`** — a true no-op for inapplicable fields. `entryAt` (when the note was authored) is preserved across edits; `updatedAt` advances only when an applicable field actually changes. To sort/filter by 'when did this happen', use `entryAt`; for 'last touched', use `updatedAt`.
removeAttachmentIdsNoAttachment ids to detach from this entry (ids from the entry's attachments array; wire shape {id, _delete: true}, verified live — removal returns the entry with the attachment gone). Other attachments are untouched. Capsule rejects removing the LAST attachment from an entry that has no content. To ADD an attachment to an existing entry, use upload_attachment with entryId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • addedInput schema / required
      Added value: +[
+  "id"
+]
  2. Changed1 schema field changedv2.2.0
    • addedInput schema / properties / removeAttachmentIds
      Added value: +{
+  "description": "Attachment ids to detach from this entry (ids from the entry's attachments array; wire shape {id, _delete: true}, verified live — removal returns the entry with the attachment gone). Other attachments are untouched. Capsule rejects removing the LAST attachment from an entry that has no content. To ADD an attachment to an existing entry, use upload_attachment with entryId.",
+  "items": {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  "minItems": 1,
+  "type": "array"
+}
  3. Addedv1.7.0
  4. Removedv1.6.2
  5. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the tool is known to mutate without being destructive. The description adds meaningful behavioral detail beyond that: 'Only the fields you supply are modified; other fields keep their current values' (partial-update/PATCH semantics) and 'Cannot change the entry's type.' It does not describe side effects like updatedAt behavior or return values, but the annotations lower the bar, and the added constraints are valuable.

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?

Three sentences with no wasted words. The purpose is front-loaded, followed by required inputs, update semantics, a hard constraint, and a usage cue. Every sentence contributes to selection or invocation.

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?

The description is largely complete for an update tool: it covers purpose, required input, partial-update behavior, type immutability, and typical usage. However, it omits the removeAttachmentIds capability entirely and over-rotates on 'note' even though the schema shows the tool also handles email-type entries. The rich schema descriptions compensate for these gaps, so this is not a major defect.

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 description coverage is 100%, so the baseline is 3. The description adds a useful cross-parameter semantic: only supplied fields are modified, which is a global PATCH rule not stated in any individual schema description. It also names content and subject as the changeable fields, though it omits removeAttachmentIds, which the schema itself documents well.

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 opens with a specific verb and resource: 'Edit an existing timeline entry — typically a note.' This clearly distinguishes it from sibling tools like add_note (create), delete_entry (delete), and get_entry (read). Stating 'Cannot change the entry's type' further sharpens the purpose boundary.

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?

The phrase 'Use this to correct or extend a note added previously' provides clear context for when to invoke the tool. It does not explicitly name sibling alternatives like add_note for creation or delete_entry for deletion, and the only exclusion mentioned is type immutability. The schema's removeAttachmentIds description does point to upload_attachment for adding attachments, which helps, but that is not in the main description.

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