Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Action

update_action
Idempotent

Update an incident action by modifying its type, description, or attachments. Send only fields you want to change; omitted fields keep their values.

Instructions

Updates the specified incident action. Supports changing the action type, description, and associated attachments. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "incident_action" in the request payload for you. 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 action 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. Procore API: Project Management > Incidents. Endpoint: PATCH /rest/v1.0/projects/{project_id}/incidents/actions/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the incident action.
form_idsNoJSON request body field — array of form IDs to attach to this action.
image_idsNoJSON request body field — array of image IDs to attach to this action.
project_idYesURL path parameter — unique identifier for the project.
upload_idsNoJSON request body field — array of upload identifiers (from the Uploads endpoint) to attach to this action.
descriptionNoJSON request body field — description of action taken, in HTML rich-text format.
incident_idNoQuery string parameter — unique identifier of the incident
action_type_idNoJSON request body field — identifier of the action type to classify this action. Obtain valid IDs from GET /rest/v1.0/companies/{company_id}/incidents/action_types.
file_version_idsNoJSON request body field — array of file version IDs to attach to this action.
drawing_revision_idsNoJSON request body field — array of drawing revision IDs to attach to this action.
run_configurable_validationsNoQuery string parameter — whether 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...
custom_field_%{custom_field_definition_id}NoJSON request body field — value 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 ...
Behavior5/5

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

Goes well beyond the annotations by disclosing partial-update behavior (omitted fields keep values), request payload nesting, the project_id default, common HTTP error codes (401/403/404), and the return payload. No contradiction with readOnlyHint:false or idempotentHint:true.

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 dense but not bloated; every sentence adds value (semantics, defaults, error handling, endpoint). It includes the Procore API section and endpoint path, which adds context but could be considered slightly verbose for a concise tool spec.

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

Completeness5/5

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

Covers all necessary invocation context: purpose, partial update, id resolution, defaults, return value, and error handling. Even without an output schema, the agent knows what to expect on success and failure, making the tool fully usable.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining that record fields are passed as top-level arguments but nested under 'incident_action' in the payload, and that project_id can be omitted thanks to the config default—details not evident in 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?

Starts with a specific verb-resource pairing: 'Updates the specified incident action.' It clearly enumerates what can be changed (action type, description, attachments), which distinguishes it from sibling tools like list_actions, create_action, show_action, and destroy_action.

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?

Provides concrete usage guidance: resolve the id with 'the matching list tool first', send only fields to change, and project_id defaults from procore_set_config. It doesn't explicitly contrast with create/destroy tools, but the update semantics and prerequisites are clearly implied and actionable.

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