Skip to main content
Glama

List time entries

list_time_entries
Read-onlyIdempotent

The time entries of a range of days that this token sees: the own time, a managed teammate's time for a manager, all time for an admin or the owner. Filter by project_id or member_id. from and to are ISO dates (YYYY-MM-DD) in the time zone of the workspace, both required, at most 366 days, both dates included. Pages: page from 1 and per_page up to 100; next_page is null on the last page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_time_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe last day: the range is at most 366 days, both dates included
fromYesThe first day
pageNoFrom 1
per_pageNo50 by default
member_idNoOnly this member
project_idNoOnly this project

Output Schema

NameRequiredDescriptionDefault
dataYes
pageYes
per_pageYes
next_pageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds genuinely new behavior: visibility is token/role dependent, dates are interpreted in the workspace time zone, the range is capped at 366 days with both endpoints inclusive. It also discloses the pagination contract, including that `next_page` is null on the final page.

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?

Four tight sentences, front-loaded with what the agent most needs: scope of visibility, then filters, then date format and limits, then pagination. No filler, though the opening clause ('The time entries of a range of days that this token sees') is slightly convoluted and has to be re-parsed.

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 six-parameter read tool with an output schema, everything an agent needs to call it correctly is present: required date bounds, format, time zone, range cap, filter semantics, and pagination termination. Return value detail is rightly left to the output schema.

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?

Schema description coverage is 100%, so the baseline would be 3, but the description adds meaning the schema does not carry: time zone interpretation for `from`/`to`, the 366-day maximum, inclusive endpoints, and the page-1/100-per-page bounds tied to `next_page`. The project_id/member_id filters get less elaboration than they could.

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?

States a specific verb and resource ('the time entries of a range of days') and immediately defines the visibility scope by role — own time, a managed teammate's time for a manager, all time for admin/owner. That scope statement distinguishes it from get_time_entry and from the other list_* siblings without requiring the agent to open a schema.

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?

Gives concrete selection criteria ('Filter by `project_id` or `member_id`') and clarifies who sees what based on token privileges, which tells the agent when this tool is the right one. It stops short of naming an alternative tool or stating exclusions explicitly, so it falls just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources