Skip to main content
Glama
MakarGlavanar

WEEEK MCP Server

weeek_create_task

Create a new task in WEEEK by providing a title and project ID. Optionally set description, board, column, priority, assignee, and due date.

Instructions

Create a NEW task in WEEEK. WRITE OPERATION — the MCP client may prompt for user confirmation before this runs. Required: title and project_id. Optional: description, board_id, board_column_id (status), priority, assignee_id, due_date. Returns the created task object in the same shape as weeek_get_task. Use this ONLY when creating a brand-new task; to change an existing task's fields use weeek_update_task, to move it to a different column use weeek_move_task, to mark it done use weeek_complete_task. All *_id parameters must come from the corresponding list tools — do not guess IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title. Required. Shown as the task's headline in WEEEK.
board_idNoBoard to place the task on. Optional. Obtain from weeek_list_boards. If omitted, WEEEK assigns to the project's default board.
date_endNoDue date in ISO 8601 format (e.g. 2026-04-15 or 2026-04-15T12:00:00Z). Optional. WEEEK's task model uses dateEnd, not dueDate.
priorityNoTask priority as an integer (WEEEK uses numeric priority levels, e.g. 0=none, 1=low, 2=medium, 3=high). Optional.
project_idYesWEEEK project ID. Required. Obtain from weeek_list_projects — do not guess.
assignee_idNoWEEEK user UUID to assign as primary. Optional. Obtain from weeek_list_workspace_members — do not guess IDs.
descriptionNoTask description / body. Optional. Plain text; WEEEK may render basic formatting.
board_column_idNoColumn (status) to place the task in. Optional. Obtain from weeek_list_board_columns. Determines the task's initial status.
Behavior4/5

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

Discloses that it's a WRITE OPERATION and may prompt for confirmation. No annotations are present, so the description carries the burden. It could mention side effects like notifications or dependencies, but overall sufficient.

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?

Well-structured with front-loaded purpose, parameter requirements, and usage guidelines. Slightly lengthy but every sentence adds value. Could be more concise by combining a few sentences.

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?

Given 8 parameters with 2 required, no output schema, and no annotations, the description is thorough: explains all parameters, return shape (same as weeek_get_task), and provides contextual guidance for ID sources and sibling tool differentiation.

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 description coverage, the description adds significant value by explaining where to obtain IDs (list tools), format expectations (ISO 8601 dates, integer priority), and optional behaviors (default board assignment).

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 creates a NEW task in WEEEK, specifies required parameters (title, project_id), and distinguishes from sibling tools like weeek_update_task, weeek_move_task, and weeek_complete_task.

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?

Explicitly states when to use this tool (creating a brand-new task) and when not to (use update, move, complete instead). Also warns not to guess IDs, directing to list tools.

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