weeek-mcp-smart

weeek_list_tasks

List WEEEK tasks with server-side filters for project, board, column, assignee, completion, priority, type, search, and date ranges to find matching work items.

Instructions

List WEEEK tasks with server-side filters: project, board, column, assignee (userId), completion, free-text search, priority, type, a single day or a startDate–endDate range (dd.mm.yyyy), completion dates. Set allPages=true together with userId, startDate, and endDate to fetch every matching page inside the connector without returning unrelated workspace pages.

Input Schema

Name	Required	Description
`all`	No	Include completed and deleted tasks; when set, `completed` is ignored.
`day`	No
`type`	No
`limit`	No
`offset`	No
`search`	No	Text to find in titles and descriptions.
`sortBy`	No
`userId`	No
`boardId`	No
`endDate`	No
`allPages`	No
`priority`	No
`completed`	No
`projectId`	No
`startDate`	No
`boardColumnId`	No
`completedAtTo`	No
`completedAtFrom`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.7.0Oct 15, 2026

addedInput schema / properties / all

Added value: +{
+  "description": "Include completed and deleted tasks; when set, `completed` is ignored.",
+  "type": "boolean"
+}

addedInput schema / properties / boardColumnId
```
Added value: +{
+  "type": "integer"
+}
```
addedInput schema / properties / boardId
```
Added value: +{
+  "type": "integer"
+}
```

addedInput schema / properties / completedAtFrom

Added value: +{
+  "$ref": "#/properties/day"
+}

addedInput schema / properties / completedAtTo

Added value: +{
+  "$ref": "#/properties/day"
+}

addedInput schema / properties / day

Added value: +{
+  "pattern": "^\\d{2}\\.\\d{2}\\.\\d{4}$",
+  "type": "string"
+}

addedInput schema / properties / endDate / $ref
```
Added value: +"#/properties/day"
```
removedInput schema / properties / endDate / pattern
```
Removed value: -"^\\d{2}\\.\\d{2}\\.\\d{4}$"
```
removedInput schema / properties / endDate / type
```
Removed value: -"string"
```

addedInput schema / properties / priority

Added value: +{
+  "enum": [
+    "low",
+    "medium",
+    "high",
+    "hold"
+  ],
+  "type": "string"
+}

addedInput schema / properties / search

Added value: +{
+  "description": "Text to find in titles and descriptions.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / startDate / $ref
```
Added value: +"#/properties/day"
```
removedInput schema / properties / startDate / pattern
```
Removed value: -"^\\d{2}\\.\\d{2}\\.\\d{4}$"
```
removedInput schema / properties / startDate / type
```
Removed value: -"string"
```

addedInput schema / properties / type

Added value: +{
+  "enum": [
+    "action",
+    "meet",
+    "call"
+  ],
+  "type": "string"
+}

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add genuine behavior beyond the schema — server-side (not client-side) filtering and the precise allPages scoping semantics — but says nothing about permissions, result ordering, or paging limits, leaving meaningful gaps for an 18-parameter tool.

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?

The filter enumeration is front-loaded in one dense sentence followed by a targeted pagination sentence; there is little wasted text. The opening sentence is long but every clause carries a distinct filter concept.

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 large-schema list tool with no output schema and no annotations, the description covers the filter dimensions and the non-obvious allPages paging behavior, which is what an agent needs to invoke it correctly. Gaps remain around sort/limit/offset defaults and default completed/deleted inclusion.

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?

With schema description coverage at only 11%, the description compensates well: it maps project, board, column, assignee/userId, completion, search, priority, type, day, and start/end and completion date ranges to readable meaning, and renders the dd.mm.yyyy date format that the schema leaves as an opaque regex. It omits limit, offset, sortBy, and 'all' semantics.

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 ('List WEEEK tasks') and immediately enumerates the filter surface, so an agent knows exactly what the tool returns. It does not explicitly name a sibling (e.g., weeek_get_task for a single task), but the plural list scope is unambiguous.

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 conditional usage guidance: 'Set allPages=true together with userId, startDate, and endDate to fetch every matching page inside the connector without returning unrelated workspace pages.' That is a clear when-to-use rule, though it offers no when-not-to-use or named alternative tools.

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

weeek_list_tasks

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools