Skip to main content
Glama
TylerIlunga

Procore MCP Server

update_incident

Modify incident details in Procore projects to update information like status, assignees, descriptions, attachments, and related records for safety and compliance tracking.

Instructions

Update Incident. [Project Management/Incidents] PATCH /rest/v1.0/projects/{project_id}/incidents/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
idYesIncident ID
run_configurable_validationsNoWhether or not Configurable validations from the Incident/Injury Configurable Field Set should be run (default: false). See (https://developers.procore.com/reference/configurable-field-sets#list-pr...
descriptionNoDescription of the Incident
event_dateNoIso8601 datetime of Incident occurrence. If time is unknown, send in the date at 0:00 project time converted to UTC.
type_idNoThe ID of the Incident Type. Defaults to the company's General type if not provided. The type must be active.
custom_status_idNoThe ID of the Custom Status. Mutually exclusive with the status field — setting one sets the other. Not updatable if the Incident has a workflows instance.
assignee_idsNoAn array of Login Information IDs to assign to the Incident. Assignees gain visibility into the Incident and its related records. Not updatable if the Incident has a workflows instance.
distribution_member_idsNoAn Array of the IDs of the Distribution Members (Not updatable if an incident has a workflows instance)
privateNoIndicates whether an Incident is private
recordableNoIndicates whether an Incident is recordable
statusNoStatus (Not updatable if an incident has a workflows instance)
time_unknownNoIndicates that the time of the Incident occurrence is unknown
titleNoIncident Title
contributing_behavior_idNoThe ID of a Contributing Behavior
contributing_condition_idNoThe ID of a Contributing Condition
hazard_idNoThe ID of a Hazard
location_idNoThe ID of a Location
environmentalsNoAssociated Environmentals to create
injuriesNoAssociated Injuries to create
near_missesNoAssociated Near Misses to create
property_damagesNoAssociated Property Damages to create
witness_statements_attributesNoAssociated Witness Statement to create
upload_uuidsNoArray of uploaded file UUIDs.
custom_field_%{custom_field_definition_id}NoValue 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 ...
drawing_revision_idsNoDrawing Revisions to attach to the response
file_version_idsNoFile Versions to attach to the response
form_idsNoForms to attach to the response
image_idsNoImages to attach to the response
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Update Incident' and an endpoint, failing to describe that this is a mutation operation, potential side effects (e.g., modifying incident data), permissions required, or any constraints like rate limits. This leaves critical behavioral traits undisclosed.

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 with three parts: action, category, and endpoint. It is front-loaded with the main purpose, though minimal. There is no wasted verbiage, but it could be more informative. The structure is clear but under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (29 parameters, no output schema, no annotations), the description is inadequate. It does not explain the tool's role in incident management, what 'update' entails, or the expected outcomes. For a mutation tool with many parameters, more context is needed to guide the agent effectively.

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 description coverage is 100%, with detailed parameter descriptions in the input schema. The description adds no parameter information beyond what the schema provides. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description neither compensates nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update Incident' is a tautology that restates the tool name without adding clarity. It includes a category '[Project Management/Incidents]' and endpoint 'PATCH /rest/v1.0/projects/{project_id}/incidents/{id}', but these do not explain what the tool does beyond the obvious 'update' action. It lacks a specific verb-resource combination or distinction from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or sibling tools like 'create_incident' or 'delete_incident' from the list. Without any usage context, an agent cannot make informed decisions.

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