Skip to main content
Glama
MakarGlavanar

WEEEK MCP Server

weeek_list_tasks

List tasks in WEEEK with optional filters by project, board, column, assignee, or completion status. Returns paginated results with key task information for 'what needs doing?' queries.

Instructions

List tasks in WEEEK with optional filters. This is the PRIMARY tool for 'what needs doing?' queries. Filter by project_id, board_id, column_id (status), assignee_id, or is_completed. Pagination is ENFORCED: default 20, max 50 per response, to stay under the 25k-token MCP response cap — call again with a higher offset if more are needed. Returns shaped tasks with id, title, projectId, boardId, boardColumnId, assigneeId, isCompleted, priority, dueDate. For full task description and details, use weeek_get_task with an id returned here. All *_id parameters must come from weeek_list_projects / weeek_list_boards / weeek_list_board_columns — do not guess IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return (1-50, default: 20). Default protects against 25k-token MCP response cap.
offsetNoNumber of items to skip for pagination (default: 0)
board_idNoFilter to tasks on this board. Obtain from weeek_list_boards.
column_idNoFilter to tasks in this column (status). Obtain from weeek_list_board_columns.
project_idNoFilter to tasks in this project. Obtain from weeek_list_projects.
assignee_idNoFilter to tasks assigned to this user (WEEEK user UUID). Obtain from weeek_list_workspace_members.
is_completedNoIf true, return only completed tasks; if false, only open; if omitted, both.
Behavior5/5

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

Discloses enforced pagination (default 20, max 50) with rationale (25k-token cap), describes the return shape (specific fields), and clarifies that full details require a separate tool call. No annotations exist to contradict.

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?

Compact (~120 words) yet comprehensive; every sentence adds value with no redundancy. Front-loaded with purpose and key instructions.

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

Completeness5/5

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

For a 7-param list tool with no output schema and no annotations, the description covers filters, pagination, return shape, limitations, dependencies, and alternative tool usage. Thorough and complete.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds critical context: each filter parameter must come from designated tools (weeek_list_boards, etc.), explains pagination defaults and limits, and clarifies is_completed behavior. This goes well beyond the schema.

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 clearly states it lists tasks with optional filters and positions itself as the PRIMARY tool for 'what needs doing?' queries, distinguishing it from sibling tools that list other entities (boards, projects, etc.) or retrieve full task details.

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

Usage Guidelines5/5

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

Provides explicit when-to-use context, explains filtering options, pagination behavior, and cautions against guessing IDs, directing the agent to companion tools for valid parameter values.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MakarGlavanar/weeek-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server