Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Productivity Log

update_productivity_log
Idempotent

Update a productivity log entry without overwriting unspecified fields. Send only the fields you need to change, along with project and log IDs, to get the updated record.

Instructions

Update single Productivity Log. #### See - Daily Log guide - for additional info on * Attachments. Send only the fields you intend to change; omitted fields keep their current values. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified productivity log on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, id, productivity_log. Procore API: Project Management > Daily Log. Endpoint: PATCH /rest/v1.0/projects/{project_id}/productivity_logs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Daily Log resource
project_idYesURL path parameter — unique identifier for the project.
productivity_logYesJSON request body field — the productivity log for this Daily Log operation
Behavior5/5

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

Annotations already mark this as a mutating (readOnly=false) but non-destructive operation; the description adds partial update behavior, return value, and common HTTP error meanings. This exceeds the safety profile provided by 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 text is dense with useful information—endpoint, error codes, partial-update semantics—and is mostly front-loaded. The markdown link and repeated required-params list add a bit of noise but don't waste sentences.

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 no output schema, the description sufficiently covers return value and error payloads. It references the Daily Log guide for fields and attachments, which compensates for the open-world productivity_log object, but leaves some field-level details implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description clarifies that id must reference an existing record, that project_id can fall back to procore_set_config, and that productivity_log is a partial update object. However, the statement that project_id may be omitted conflicts with the schema's required array, creating ambiguity.

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 opens with the specific action 'Update single Productivity Log' and includes the PATCH endpoint, making the operation unambiguous. The phrase 'single' and the instruction to resolve an existing id help distinguish it from create/list/delete siblings.

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?

It tells the agent to send only changed fields and to resolve the id with the matching list tool first, which is practical usage guidance. It also explains project_id fallback to config, though it does not explicitly contrast when update should be chosen over create/list/delete.

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