Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Edit Tracker entity checklist

tracker_entities_checklists_update
Idempotent

Replace or update all checklist items for a Tracker project, portfolio, or goal in one call. Returns the entity with its updated checklist.

Instructions

Replace/update a Tracker entity's checklist items in one call.

body is a bare array of items, each with id/text/checked. To edit a single item by id use entities_checklists_items_update. Returns the entity with its checklist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesA bare array of checklist items.
expandNoExtra blocks to include in the reply.
fieldsNoComma-separated fields to include in the reply.
notifyNoNotify the users in the fields of the object; omitted, the API notifies.
entity_idYesEntity id (or shortId).
entity_typeYesEntity type: ``project``, ``portfolio`` or ``goal``.
notify_authorNoNotify the author of the change; omitted, the API does not.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.122.1
    • changedInput schema / properties / body / items / properties / deadline / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "description": "Typed ``deadline`` block for a checklist item or key result write body.",
-    "properties": {
-      "date": {
-        "description": "Deadline date, YYYY-MM-DDThh:mm:ss.sss±hhmm.",
-        "type": "string"
-      },
-      "deadlineType": {
-        "default": "date",
-        "description": "Deadline kind: 'date' or 'quarter'.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "date"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "description": "Typed ``deadline`` block for a checklist item or key result write body.",
+    "properties": {
+      "date": {
+        "description": "Deadline date, YYYY-MM-DDThh:mm:ss.sss±hhmm.",
+        "type": "string"
+      },
+      "deadlineType": {
+        "description": "Deadline kind: 'date' or 'quarter'.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "date",
+      "deadlineType"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observedv0.67.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is largely covered. The description adds the body shape and the return value ("the entity with its checklist"), which is useful. However, it never resolves whether items omitted from the array are deleted or preserved — the single most important behavioral fact for this call — and the schema's "edit-all body" hint only deepens that ambiguity.

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 short sentences, front-loaded with the action and scope, then the body shape, then the sibling alternative. No filler or repetition of the title.

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

Completeness3/5

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

Return behavior is covered ("Returns the entity with its checklist"), parameters are covered by the schema, and safety by annotations. The gap is the replace-vs-merge semantics of the body array, which the description's own wording leaves unresolved for a mutation tool the agent must invoke correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (expand/fields/notify/notify_author/entity_id/entity_type/body) is already documented in the schema, giving a baseline of 3. The description restates the body array and its item keys (id/text/checked), which marginally helps but adds no format or semantics 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?

Names a concrete verb and resource: replacing/updating a Tracker entity's checklist items in a single call, and explicitly contrasts with the sibling that edits one item. The only weakness is the hedged verb pair "Replace/update," which leaves the agent unsure whether this is a full replacement or a merge.

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?

Gives an explicit routing rule: to edit a single item by id, use ``entities_checklists_items_update`` instead. That is a real when-to-use-alternative statement. It stops short of covering the other checklist siblings (create/delete/move) or stating prerequisites such as required entity permissions.

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