Skip to main content
Glama

Create project time entry

create_project_time_entry

Create a new project time entry. Requires project_time_entries:write scope.

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": {
      "project_id": "<project_id>",
      "task_id": "<task_id>",
      "user_id": "<user_id>",
      "start_time": "<start_time>"
    },
    "name": "create_project_time_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID (required) - resolve via list_project_tasks
user_idYesUser ID (required) - an active member of the organization (see list_users)
end_timeNoEnd time (ISO 8601 datetime)
user_nameNoDisplay name of the user
project_idYesProject ID (required) - resolve via list_projects
start_timeYesStart time (ISO 8601 datetime, required)
descriptionNoDescription
is_billableNoWhether the time is billable
duration_minutesNoWhole minutes worked. Send this or start_time and end_time; if you send both, they must agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID (required)"New value: +"Project ID (required) - resolve via list_projects"
    • changedInput schema / properties / task_id / description
      Previous value: -"Task ID (required)"New value: +"Task ID (required) - resolve via list_project_tasks"
  2. Changed4 schema fields changed
    • changedInput schema / properties / duration_minutes / description
      Previous value: -"Duration worked, in minutes"New value: +"Whole minutes worked. Send this or start_time and end_time; if you send both, they must agree."
    • addedInput schema / properties / duration_minutes / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / duration_minutes / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / user_id / description
      Previous value: -"User ID (required)"New value: +"User ID (required) - an active member of the organization (see list_users)"
  3. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • addedInput schema / properties / task_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • addedInput schema / properties / task_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  6. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, so the safety profile is covered. The description adds the write-scope requirement, which is useful context, but with idempotentHint=false it should warn that repeated calls create duplicate entries — a material risk for a time-tracking tool. No contradiction with annotations.

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?

Two short sentences, front-loaded with the action, and no filler. It is efficient but perhaps too lean — the prerequisite sentence is the only one earning its place beyond the name.

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?

For a non-idempotent, nine-parameter create mutation, the description leans entirely on a rich schema and annotations. It is adequate to invoke the tool correctly, but says nothing about duplicate prevention, whether entries feed billing/cost rollups, or how the created entry is returned (no output schema exists).

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 schema already documents all nine parameters including the duration_minutes vs start_time/end_time conflict rule and the resolve-via list_* hints. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('Create') and a precise resource ('project time entry'), which cleanly separates it from create_project_task, create_project_comment, and other project siblings. It does not explicitly name update_project_time_entry or bulk_create as the alternatives, so sibling differentiation is implied rather than stated.

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?

The scope prerequisite ('requires project_time_entries:write scope') is a genuine usage gate, but there is no guidance on when to use this versus update_project_time_entry or bulk_create. Nothing about correcting a previously logged entry versus recording a new one.

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