Skip to main content
Glama
adalekin

weeek-mcp

by adalekin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

weeek_update_task

Update task fields (title, priority, type, dates, duration, tags), custom values, and description in Weeek.

Instructions

Update a task's fields (title, priority, type, dates, duration, tags), its custom field values, and its description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTag ids — weeek_manage_tags lists them with their names.
typeNo
titleNo
task_idYes
due_dateNoY-m-d
durationNoEstimate in minutes
priorityNoPriority as a number or a label: 0 low (Низкий), 1 medium (Средний), 2 high (Высокий), 3 hold (Замороженный).
start_dateNoY-m-d
descriptionNoReplaces the description, as Markdown (same feature set as weeek_kb_update); an empty string clears it. Weeek's REST API ignores the description on update, so it is written over the same collaborative channel its editor uses, and needs the knowledge base session.
custom_fieldsNoCustom field values keyed by field name or field id, e.g. {"Ссылка на фичу": "https://..."}. For a select field pass the option name or its id, for a multiselect a list of them; pass null to clear a field. Names are matched against this task's own fields, and a field that does not belong to this task's project is reported as an error.
due_date_timeNoISO 8601
start_date_timeNoISO 8601

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.2
    • changedInput schema / properties / description / description
      Previous value: -"Replaces the description, as Markdown (same feature set as weeek_kb_update); an empty string clears it. Weeek's REST API ignores the description on update, so this drives its editor in a headless browser (a few seconds) and needs the knowledge base session."New value: +"Replaces the description, as Markdown (same feature set as weeek_kb_update); an empty string clears it. Weeek's REST API ignores the description on update, so it is written over the same collaborative channel its editor uses, and needs the knowledge base session."
    • addedInput schema / properties / priority / anyOf
      Added value: +[
+  {
+    "enum": [
+      0,
+      1,
+      2,
+      3
+    ],
+    "type": "integer"
+  },
+  {
+    "enum": [
+      "low",
+      "medium",
+      "high",
+      "hold"
+    ],
+    "type": "string"
+  }
+]
    • removedInput schema / properties / priority / enum
      Removed value: -[
-  0,
-  1,
-  2,
-  3,
-  "low",
-  "medium",
-  "high",
-  "hold"
-]
    • removedInput schema / properties / priority / type
      Removed value: -[
-  "integer",
-  "string"
-]
  2. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether this is a partial merge (omitted fields left intact) or a full replace, what permissions or session it needs, whether clearing values is possible, or what the response contains. The one genuinely notable behavior — that the description is written over a collaborative channel and needs a knowledge base session — lives in the schema, not the description.

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?

A single front-loaded sentence with the verb and resource first, then the enumerated surface. Nothing is wasted, though the parenthetical list is partly redundant with the schema.

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?

With 12 parameters, a nested custom_fields object, no annotations, and no output schema, the definition is thin on the update-semantics dimension — partial vs. full update and error/failure behavior are unaddressed. The schema fills in parameter-level detail, which keeps this from being incomplete, but the description should say more about how the mutation behaves.

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 75%, above the baseline, and the schema itself carries rich parameter detail (priority label mapping, tag id sourcing, custom_fields keying and error behavior, empty-string clearing). The description's parenthetical field list largely restates what the schema already documents, so it adds marginal meaning beyond the structured fields.

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 states a specific verb ('Update') and resource ('a task') and enumerates the editable surface: fields, custom field values, and description. It is clear what the tool does, though it never distinguishes itself from specialized siblings like weeek_set_assignees, weeek_move_task, or weeek_complete_task that also mutate a task.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites, and no routing away from the many sibling mutation tools (assignees, watchers, timers, completion, move, delete). The agent must infer that this is the general field-update path from the field list alone.

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