Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Change Event

update_change_event
Idempotent

Update an existing Procore change event by sending only the fields to change. Requires the event's id and project id, returns the modified event.

Instructions

Updates an existing change event in Procore. 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 "change_event" in the request payload for you. id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified change event 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: id, project_id. Procore API (v1.1): Construction Financials > Change Events. Endpoint: PATCH /rest/v1.1/change_events/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Change Events resource
scopeNoJSON request body field — event Scope
titleNoJSON request body field — the title for this Change Events operation
numberNoJSON request body field — the number for this Change Events operation
sourceNoJSON request body field — the Change Event source refers to the resource that was responsible for creating this Change Event.
statusNoJSON request body field — the status for this Change Events operation
project_idYesQuery string parameter — unique identifier for the project.
attachmentsNoJSON request body field — not to be used if other attachment types are included
change_typeNoJSON request body field — the change type for this Change Events operation
descriptionNoJSON request body field — the description for this Change Events operation
change_itemsNoJSON request body field — change Event Line Items
event_originNoJSON request body field — the event origin for this Change Events operation
change_reasonNoJSON request body field — the change reason for this Change Events operation
custom_fieldsNoJSON request body field — the custom fields for this Change Events operation
external_dataNoJSON request body field — the external data for this Change Events operation
attachments_by_formNoJSON request body field — the attachments by form for this Change Events operation
attachments_by_uuidNoJSON request body field — the attachments by uuid for this Change Events operation
attachments_by_imageNoJSON request body field — attachments_by_image
source_of_revenue_romNoJSON request body field — revenue ROM source for this Change Event
attachments_by_file_versionNoJSON request body field — attachments_by_file_version
prime_contract_for_estimatesNoJSON request body field — prime_contract_for_estimates
attachments_by_drawing_revisionNoJSON request body field — attachments_by_drawing_revision
Behavior5/5

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

Even with annotations indicating non-read-only and idempotent behavior, the description adds significant context: partial-update semantics, automatic nesting of top-level arguments into the payload, return value, and detailed failure/error status scenarios (401, 403, 404). This goes well beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but each sentence earns its place: purpose, update semantics, payload handling, id resolution, return value, error behavior, required params, and API reference. It is well-structured and front-loaded with the core purpose.

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?

The description covers prerequisites (id resolution), mutation behavior, return value, error handling, required parameters, and API endpoint. Given that there is no output schema, it adequately explains what to expect on success and failure. It is complete for a 22-parameter update tool.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds crucial meaning beyond field names: the partial-update behavior, the fact that fields are passed top-level yet nested internally, and guidance that id must identify an existing parent record resolved via a list tool. These insights are not evident from the schema alone.

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 a specific verb and resource: "Updates an existing change event in Procore." This clearly distinguishes the tool from siblings like create_change_event, delete_change_event, and list_change_events by focusing on modifying an existing record.

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 clear usage context: says to send only fields to change, and instructs to resolve the id using the matching list tool first. It does not explicitly name alternatives (e.g., use create for new records), so it stops short of a 5.

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