Skip to main content
Glama
TylerIlunga

Procore MCP Server

Bulk Update Timecard Entries

bulk_update_timecard_entries

Update multiple timecard entries at once: provide company ID and field updates. Only supplied fields are modified; returns updated records.

Instructions

Updates multiple timecard entries at the same time. 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: company_id, updates. Procore API: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/companies/{company_id}/timesheets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
approval_statusNoJSON request body field — approval status of a Timecard Entry
billableNoJSON request body field — the Billable status of the Timecard Entry
cost_code_idNoJSON request body field — the ID of the Cost Code of the Timecard Entry
crew_idNoJSON request body field — the ID of the crew for the Timecard Entry
dateNoJSON request body field — the Date of the Timecard Entry
descriptionNoJSON request body field — the description of the Timecard Entry
hoursNoJSON request body field — hours worked on a Timecard Entry
location_idNoJSON request body field — the location ID for the Timecard Entry
origin_idNoJSON request body field — iD of related external data
origin_dataNoJSON request body field — value of related external data
party_idNoJSON request body field — the ID of the party for the Timecard Entry
project_idNoJSON request body field — the ID of the Timecard Time Type of the Timecard Entry
set_timecard_time_type_automaticallyNoJSON request body field — whether or not to allow the automatic overtime management system to apply the configured rules to set the timecard_time_type_id and/or split the timecard entry automatically
sub_job_idNoJSON request body field — the ID of the Sub Job of the Timecard Entry
time_inNoJSON request body field — time in for the Timecard Entry
time_outNoJSON request body field — time out for the Timecard Entry
timesheet_idNoJSON request body field — the ID of the Timesheet of the Timecard Entry
timecard_time_type_idNoJSON request body field — the ID of the Timecard Time Type of the Timecard Entry
updatesYesJSON request body field — the IDs of the timecards you want to update
user_idNoJSON request body field — the ID of the Login Information of the Timecard Entry
work_classification_idNoJSON request body field — the ID of the Work Classification of the Timecard Entry
Behavior4/5

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

Annotations already provide safety profile (non-destructive, not read-only). Description adds that only supplied fields are changed (partial update) and returns the modified object. This is useful context beyond 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?

The description is moderately concise with 6 sentences, but includes redundant Procore API details. Could be more streamlined without losing clarity.

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?

No output schema, so description should explain return format. It says 'returns the modified object' but no details. Also lacks error handling, atomicity, or rate limit info. Adequate for basic use but incomplete.

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 baseline 3. Description mentions required parameters (company_id, updates) but does not add new meaning to the 'updates' array structure or other fields.

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?

The description clearly states it updates multiple timecard entries and specifies the resource as 'Field Productivity records'. However, it does not distinguish this tool from sibling bulk_update_* tools, missing a chance to differentiate.

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 use this tool versus alternatives (e.g., bulk_update_timecard_entry) or when not to use it. The description only states what it does, not the context.

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