solidtime-mcp

solidtime_time_entries_export

Read-only

Export time entries as CSV, PDF, XLSX, or ODS for reporting and billing, using date ranges and filters such as projects, members, clients, and tags.

Instructions

Export time entries. GET .../time-entries/export. format csv, pdf, xlsx, or ods. start and end required by the API.

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": {
      "format": "<format>"
    },
    "name": "solidtime_time_entries_export"
  }
}

Input Schema

Name	Required	Description
`end`	No	UTC timestamp like "2000-02-22T14:58:59Z".
`type`	No
`limit`	No
`start`	No	UTC timestamp like "2000-02-22T14:58:59Z".
`active`	No
`format`	Yes
`tag_ids`	No
`billable`	No
`task_ids`	No
`member_id`	No
`client_ids`	No
`member_ids`	No
`project_ids`	No
`rounding_type`	No
`tag_match_type`	No
`only_full_dates`	No
`organization_id`	No	Organization UUID. Falls back to SOLIDTIME_ORGANIZATION_ID, then a single membership from GET /v1/users/me/memberships.
`rounding_minutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare it is a non-destructive read, so the description adds the genuinely useful constraint that start and end are required by the API even though the schema only marks `format` as required. It says nothing about pagination, size limits, or what the returned file payload looks like, which matters for an export tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded with the core action, with no filler sentences. However, the telegraphic fragments ('GET .../time-entries/export.', 'format csv, pdf, xlsx, or ods.') read like terse notes rather than coherent guidance, and the parameter list overlaps with the schema enum.

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

Completeness2/5

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

An 18-parameter export tool with no output schema needs far more explanation of filtering, rounding, and format trade-offs than three fragments provide. The definition covers the minimum to trigger a call but not enough to call it correctly with non-trivial filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% across 18 parameters, so the description must compensate and largely does not. It clarifies `format` and flags start/end, but leaves filters (member_ids, project_ids, client_ids, tag_ids, task_ids), rounding_type/rounding_minutes, tag_match_type, only_full_dates, active, billable, limit, and organization_id entirely undocumented.

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 ('Export time entries') so an agent knows exactly what the tool produces. It does not distinguish itself from the nearby `solidtime_time_entries_aggregate_export` or `solidtime_time_entries_list`, which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

No guidance on when to choose this over listing time entries or the aggregate export, and no mention of prerequisites beyond the implicit date range. The agent has to infer the use case (file download in a chosen format) entirely from the name.

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

Deploy Server