InstaClock

List time entries

list_time_entries

Read-onlyIdempotent

List time entries in a date range, newest first, optionally for one activity. Dates are in the user's timezone. Returns a cursor when there are more.

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

Name	Required	Description
`to`	Yes	Last day to include, YYYY-MM-DD
`from`	Yes	First day to include, YYYY-MM-DD
`limit`	No	Default 25
`cursor`	No	Cursor from a previous call
`activityId`	No	Activity id from list_activities
`activityName`	No	Activity name, when the id is not known. Case-insensitive; prefix matches work.

Output Schema

Name	Required	Description
`entries`	Yes
`timezone`	Yes	The user's IANA timezone. Times in this result are in this zone.
`nextCursor`	Yes	Pass as cursor to get the next page; null when there are no more

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavior beyond that: newest-first ordering, user-timezone date semantics, and that a cursor is returned when more results exist.

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?

Three compact sentences, no filler, with the core scope and ordering front-loaded before the pagination note. Every clause (timezone, cursor) carries information an agent needs.

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

Completeness4/5

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

An output schema exists, so return shapes need not be explained, and annotations cover safety. Combined with the description's notes on ordering, timezone, and pagination, an agent has enough to call it correctly; only explicit sibling routing is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning not in the schema: it clarifies that the date bounds are interpreted in the user's timezone and that cursor should be passed back when more pages exist. It still leaves limit behavior and the activityId/activityName tradeoff to the schema.

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?

States a specific verb and resource ("List time entries") plus scope details: date range, newest-first ordering, optional single-activity filter. It is clearly distinct from siblings like list_activities or get_summary, though it never names them explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the required date range and the optional activity filter, but there is no explicit when-to-use guidance or exclusion (e.g. "use get_summary for aggregates" or "use get_weekly_review for rollups"). The agent must infer routing among the 16 siblings.

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

All InstaClock tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?