Skip to main content
Glama

start_timer

Start a timer to track time spent on a task. Provide task ID; optionally supply board ID to avoid an extra API request.

Instructions

Start a new time tracker on a task for the authenticated user.

Returns the created TimeTracker. The new timer starts in the running state (ended_at is None); call stop_timer when work pauses or ends.

board_id is required by the Kanban Tool API but may be omitted here — when not supplied the tool resolves it via an internal get_task(task_id) call (one extra HTTP round-trip). Pass it explicitly when you already have it (e.g. you just listed tasks for a board) to avoid the second request. Either way, the resulting wire body sends both ids.

Note: timers are per-user — starting one creates a record for the authenticated user only. Use whoami if you need to know whose timer it is.

Common 422: the API rejects starting a timer on a task whose board you don't have access to with a typed KanbanToolValidationError. Verify the task is on a board you can list via list_boards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
board_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
user_idNo
board_idNo
task_idNo
started_atNo
ended_atNo
listedNo
sprint_idNo
seconds_from_resumed_sprintNo
positionNo
highlighted_atNo
enlist_atNo
created_atNo
updated_atNo
is_runningYesTrue iff the timer is still active (no ``ended_at`` set).
Behavior5/5

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

Annotations are minimal (only idempotent hints), but the description details the running state, per-user nature, board_id resolution mechanism with extra round-trip, and error conditions. No contradictions with annotations.

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 description is thorough but slightly verbose; however, every sentence adds value. It front-loads the core purpose and organizes additional details in separate paragraphs.

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 the tool's complexity and the presence of an output schema, the description covers return value characteristics, error handling, performance optimization, and user scope. Nothing essential is missing.

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?

With 0% schema description coverage, the description fully explains both parameters: task_id as required, board_id as optional with performance implications. Adds meaning beyond the schema's type and constraints.

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 explicitly states 'Start a new time tracker on a task for the authenticated user,' providing a specific verb and resource. It clearly distinguishes from sibling tools like stop_timer and list_my_timers.

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?

The description provides explicit guidance: when to use (starting a timer), when to call stop_timer, tips for optimizing board_id, and common error scenarios. References sibling tools like whoami and list_boards.

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/VeryLongOrgNameSuchWow/kanbantool-mcp'

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