Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Change Event

create_change_event

Create a new Change Event in Procore. Requires project ID, scope, and status; returns the created object on success.

Instructions

Create Change Event. Use this to create a new Change Events in Procore. Creates a new Change Events and returns the created object on success (HTTP 201). Required parameters: project_id, scope, status. Procore API (v1.1): Construction Financials > Change Events. Endpoint: POST /rest/v1.1/change_events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
numberNoJSON request body field — the number for this Change Events operation
titleNoJSON request body field — the title for this Change Events operation
descriptionNoJSON request body field — the description for this Change Events operation
scopeYesJSON request body field — event Scope
prime_contract_for_estimatesNoJSON request body field — prime_contract_for_estimates
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
statusYesJSON request body field — the status 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.
source_of_revenue_romNoJSON request body field — revenue ROM source for this Change Event
change_typeNoJSON request body field — the change type for this Change Events operation
external_dataNoJSON request body field — the external data for this Change Events operation
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 ...
change_itemsNoJSON request body field — change Event Line Items
Behavior3/5

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

Annotations already indicate a write operation (readOnlyHint false) and non-destructive behavior. The description adds that it returns the created object on success (HTTP 201) and mentions the API version and endpoint. However, it does not disclose side effects (openWorldHint true is unaddressed), permissions, or potential state changes beyond creation.

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 four sentences long and front-loaded with the tool's purpose. It includes required parameters and endpoint details without extraneous content. It is efficient but could be more structured (e.g., bullet points) for scanning.

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 tool's complexity (15 parameters, many nested objects) and lack of output schema, the description is insufficient. It does not explain the role of nested objects or provide guidance on how to populate them. The agent would need to rely solely on the schema, which lacks structure for several fields.

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%, so the schema already describes each parameter. The description lists the three required parameters but adds no extra meaning beyond that. It does not explain the purpose or structure of nested objects like event_origin or change_reason, which are defined with 'additionalProperties' in the schema.

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

Purpose4/5

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

The description clearly states the verb 'Create' and the resource 'Change Events', and notes the endpoint. It is specific about the action but does not distinguish from sibling tools like clone_change_event or update_change_event. A clear purpose but lacking differentiation.

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?

The description only states what the tool does and lists required parameters. It provides no guidance on when to use this tool versus alternatives (e.g., update_change_event, clone_change_event). The agent has no basis to choose among similar tools.

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