Skip to main content
Glama
TylerIlunga

Procore MCP Server

Edit A Timecard Entry

edit_a_timecard_entry

Update an existing timecard entry for a project. Modify hours, times, billable status, or other fields to correct or adjust labor tracking.

Instructions

Update Timecard Entry associated with the specific Project. Use this to update an existing Field Productivity records (only the supplied fields are changed). Updates the specified Field Productivity records and returns the modified object on success. Required parameters: project_id, id. Procore API (v1.1): Project Management > Field Productivity. Endpoint: PATCH /rest/v1.1/projects/{project_id}/project_timecard_entries/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — iD of the Timecard Entry
hoursNoJSON request body field — total number of hours worked (excluding breaks) for the timecard entry. This property is not required if the timesheet time entry is configured for start time and stop time.
lunch_timeNoJSON request body field — the duration of the lunch break, in minutes, for the Timecard Entry. This property is only required if the timesheet time entry is configured for start time and stop time.
time_inNoJSON request body field — the start time of the Timecard Entry in ISO 8601 format. This property is only required if the timesheet time entry is configured for start time and stop time.
time_outNoJSON request body field — the stop time of the Timecard Entry in ISO 8601 format. This property is only required if the timesheet time entry is configured for start time and stop time.
billableNoJSON request body field — the billable status of the Timecard Entry. Must be either true or false.
dateNoJSON request body field — the date of the Timecard Entry in ISO 8601 format.
descriptionNoJSON request body field — the description of the Timecard Entry.
timecard_time_type_idNoJSON request body field — the ID of the Timecard Time Type corresponding to the Timecard Entry property.
timesheet_idNoJSON request body field — the ID of the Timesheet corresponding to the Timecard Entry property.
cost_code_idNoJSON request body field — the ID of the Cost Code corresponding to the Timecard Entry property.
sub_job_idNoJSON request body field — the ID of the Subjob corresponding to the Timecard Entry property.
location_idNoJSON request body field — the ID of the Location corresponding to the Timecard Entry property.
login_information_idNoJSON request body field — the ID of the Login Information corresponding to the Timecard Entry property.
party_idNoJSON request body field — the ID of the Party corresponding to the Timecard Entry property.
origin_idNoJSON request body field — the ID of the related external data.
origin_dataNoJSON request body field — the value of the related external data.
line_item_type_idNoJSON request body field — the ID of the line item type corresponding to the time card entry.
custom_field_%{custom_field_definition_id}NoJSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds useful context by specifying partial update ('only the supplied fields are changed') and that it returns the modified object, aligning with the PATCH method.

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?

The description is concise, with only three sentences covering purpose, behavior, required parameters, and API endpoint. It is front-loaded with the main action and uses no unnecessary words.

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?

Given the tool's 20 parameters and lack of output schema, the description covers the essential aspects: purpose, partial update, return of modified object, required parameters, and API version. It could mention error handling or permissions but is adequate for a PATCH operation.

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 the input schema already describes all parameters thoroughly. The description only mentions required parameters (project_id, id) and does not add extra meaning beyond what's in the schema.

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 clearly states the verb 'Update' and the resource 'Timecard Entry', and specifies it is for an existing record associated with a specific Project. It distinguishes from sibling create/delete tools by focusing on updating existing Field Productivity records.

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 description mentions when to use the tool (to update an existing record) but does not provide explicit guidance on when not to use it or suggest alternative tools. It lacks comparison to similar tools like create_timecard_entry or delete_timecard_entry.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TylerIlunga/procore-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server