Skip to main content
Glama
timesheetIO

Timesheet MCP Server

Official
by timesheetIO

List Tasks

task_list
Read-only

Retrieve and filter tracked time entries by date, project, team, or user. Supports pagination to control how many tasks are returned.

Instructions

Use this when the user wants to view their time entries. IMPORTANT: When the user asks for a specific number (e.g., "show me 10 tasks"), use the limit parameter to control how many tasks are returned. Always use pagination to avoid loading all tasks unnecessarily. Supports extensive filtering by organization, team, project, user, tags, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tasks to return. Use this when user asks for a specific number (e.g., "10 tasks" = limit: 10). Defaults to 20 if not specified.
pageNoPage number for pagination (1-based). Use with limit to fetch subsequent pages.
sortNoSort field for tasks: dateTime=by start/end time, time=by duration, created=by creation date
orderNoSort order (ascending or descending)
startDateNoFilter tasks starting on or after this date (YYYY-MM-DD format)
endDateNoFilter tasks ending on or before this date (YYYY-MM-DD format)
organizationIdNoFilter tasks by organization ID
teamIdNoFilter tasks by team ID
teamIdsNoFilter tasks by multiple team IDs
projectIdNoFilter tasks for a specific project
projectIdsNoFilter tasks by multiple project IDs
todoIdNoFilter tasks associated with a specific todo/task item
taskIdsNoFilter specific tasks by IDs
rateIdNoFilter tasks by rate/billing rate ID
documentIdNoFilter tasks associated with a specific document
typeNoFilter tasks by type: all=all types, task=regular time entries, mileage=mileage entries, call=call entries
filterNoFilter tasks by billing/payment status: all=all tasks, billable=only billable, notBillable=non-billable, paid=payment received, unpaid=not paid, billed=invoice sent, outstanding=billed but unpaid
excludeTaskIdsNoExclude specific task IDs from results
tagIdsNoFilter tasks by tag IDs
userIdsNoFilter tasks by user IDs (task owners)
feelingsNoFilter tasks by feeling/satisfaction ratings (1-5)
populatePausesNoInclude pause/break information in task details
populateExpensesNoInclude expense information in task details
populateNotesNoInclude notes in task details
populateTagsNoInclude tag details in task information

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYesList of tasks matching the criteria
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description reinforces read-only behavior only implicitly and adds pagination guidance. It does not disclose anything beyond what annotations provide, but there is no contradiction.

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 three sentences, front-loading the usage instruction. It is concise and informative, though the mention of extensive filtering is redundant given the schema. No wasted sentences.

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?

Given the tool's complexity (25 parameters, output schema exists), the description covers usage and filtering but lacks details about default pagination, error handling, or edge cases. The annotations and schema fill some gaps, making it adequate but not complete.

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 100%, so the baseline is 3. The description only emphasizes the limit parameter usage without adding new meaning to other parameters. It does not compensate with examples or relationships.

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 starts with 'Use this when the user wants to view their time entries,' which clearly identifies the action and resource. The distinction from siblings like task_get (single task) is implied, but the phrasing 'time entries' may cause slight confusion since the tool lists tasks (which include time entries). Still, the verb and resource are identifiable.

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?

The description explicitly states when to use this tool ('view their time entries') and provides an important hint about using the limit parameter when a specific number is requested. It also advises using pagination. It does not explicitly exclude alternatives, but the context is clear enough.

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/timesheetIO/timesheet-mcp'

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