Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Time And Material Entry

update_a_time_and_material_entry

Update a Time and Material entry for a project by specifying the project ID and entry ID, modifying fields such as name, status, description, and attachments.

Instructions

Updating a Time And Material Entry associated with the specified 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: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/projects/{project_id}/time_and_material_entries/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — id of the Time And Material Entry
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
nameNoJSON request body field — the title of T&M ticket
reference_numberNoJSON request body field — the refrence number associate with T&M ticket
descriptionNoJSON request body field — the description of job
statusNoJSON request body field — current status of T&M ticket
privateNoJSON request body field — if the T&M ticket is private
numberNoJSON request body field — unique number for the T&M ticket
customer_signature_idNoJSON request body field — the ID associate with customer's signature
company_signature_idNoJSON request body field — the ID associate with company's signature
company_signee_party_idNoJSON request body field — the ID associate with company's signature party
customer_signee_party_idNoJSON request body field — the ID associate with customer's signature party
work_performed_on_dateNoJSON request body field — date work performed on
drawing_revision_idsNoJSON request body field — drawing Revisions to attach to the response
file_version_idsNoJSON request body field — file Versions to attach to the response
form_idsNoJSON request body field — forms to attach to the response
image_idsNoJSON request body field — images to attach to the response
upload_idsNoJSON request body field — the specified array of upload ids is saved as Time And Material Entry Attachments.
Behavior4/5

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

The description adds value beyond annotations by specifying the update is partial (only supplied fields changed), using HTTP PATCH method, and returning the modified object. Annotations already indicate it's a non-destructive mutation, so the description complements them well.

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 concise, front-loaded with the main purpose, and efficiently conveys key details. The API endpoint adds some length but is useful context.

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?

Given the complexity (19 parameters, no output schema), the description covers core behavior but is vague about the return object ('returns the modified object'). More guidance on the response structure or common fields would improve completeness.

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?

The input schema has 100% description coverage for all 19 parameters, so the schema itself provides ample meaning. The description merely restates required parameters, adding no new parameter semantics. Baseline score of 3 is appropriate.

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 tool updates an existing Time And Material Entry, specifies it performs a partial update (only supplied fields are changed), and returns the modified object. It distinguishes from sibling tools like create, delete, and update_multiple by focusing on single-entry update.

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?

The description explicitly states the tool is for updating existing records, which implies it should not be used for creating or deleting. However, it does not reference sibling tools or provide explicit when-not-to-use scenarios, so clarity is good but not perfect.

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