Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Work Log

update_work_log

Update an existing work log record in a Procore project, modifying only the supplied fields such as hours, description, or status.

Instructions

Update single Work Log. #### See - Daily Log guide - for additional info on * Attachments. Use this to update an existing Daily Log records (only the supplied fields are changed). Updates the specified Daily Log records and returns the modified object on success. Required parameters: project_id, id, work_log. Procore API: Project Management > Daily Log. Endpoint: PATCH /rest/v1.0/projects/{project_id}/work_logs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Daily Log resource
work_logYesJSON request body field — the work log for this Daily Log operation
attachmentsNoJSON request body field — scheduled Work Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-dat...
Behavior3/5

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

Annotations indicate not read-only, not destructive, not idempotent. Description adds that only supplied fields change and returns modified object, but doesn't significantly extend behavioral understanding 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?

Description is reasonably concise and front-loaded, but includes technical detail like the API endpoint which may not be essential for tool selection.

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?

Covers purpose, parameters, basic behavior, and links to external guide. Lacks error cases or prerequisites beyond required params, but acceptable for a simple update tool.

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% with parameter descriptions. The description only repeats required parameters and provides no additional meaning beyond 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 'Update single Work Log' and specifies it updates existing Daily Log records with only supplied fields, returning the modified object. It differentiates from siblings by targeting a single resource.

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 vs alternatives. It does not mention when not to use it or provide comparisons to other update tools among many siblings.

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