Skip to main content
Glama

Update time entry descriptions in bulk

bulk_update_time_reports
DestructiveIdempotent

Apply a common text description update to multiple of your own time entries. Supply ids (list of time-report ids, max 100) and text (the new description). Returns per-id results — partial failures are reported rather than aborting the whole batch.

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": {
      "ids": "<ids>",
      "text": "<text>"
    },
    "name": "bulk_update_time_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesIds of the time entries to update (max 100).
textYesNew description to apply to all entries (max 1000 characters).
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description goes beyond them by stating the batch cap (max 100) and that partial failures are returned per-id rather than aborting the batch. It still doesn't say that existing descriptions are overwritten irreversibly or whether the operation is atomic in any respect, so it falls just short of full disclosure.

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 short sentences, zero filler: scope first, then the required inputs and limit, then the return/failure behavior. Every sentence 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?

With no output schema, the description usefully explains the return shape (per-id results with partial failures reported) and the batch limit, which is enough to call it correctly. Minor gap: it doesn't clarify ownership restrictions in failure cases (e.g. ids belonging to others) or rate/throughput expectations for 100-item batches.

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 coverage is 100%, so ids, text, and idempotency_key are already fully documented; the description only restates ids and text and repeats the 100-item cap. It adds no new meaning about parameter behavior beyond the schema, so the baseline 3 applies.

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 gives a specific verb (apply), resource (time entries), operation (common text description update) and scope (multiple of your own entries), which cleanly separates it from the single-entry update_time_report and from bulk_create_time_reports. An agent can identify the tool without opening the 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?

It makes the batch condition clear ('multiple of your own time entries', 'common text') which implies single-entry edits belong elsewhere, but it never explicitly names update_time_report as the alternative for one-off changes or states exclusions. Clear context, no explicit when-not guidance.

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