Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Timeline Event

update_timeline_event

Partially update a timeline event in Procore Scheduling by providing only the fields to change. Unspecified fields remain unchanged.

Instructions

Partially update a timeline event. Only provided fields will be updated. Use this to update an existing Scheduling records (only the supplied fields are changed). Updates the specified Scheduling records and returns the modified object on success. Required parameters: company_id, project_id, schedule_id, timeline_event_id, timeline_event_type. Procore API (v2.0): Project Management > Scheduling. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/schedules/{schedule_id}/timeline_events/{timeline_event_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company
project_idYesURL path parameter — unique identifier for the project
schedule_idYesURL path parameter — unique identifier for the schedule
timeline_event_idYesURL path parameter — unique identifier of the timeline event
timeline_event_nameNoJSON request body field — the descriptive name of the timeline event
start_dateNoJSON request body field — the timeline event start date (ISO 8601 format)
finish_dateNoJSON request body field — the timeline event finish date (ISO 8601 format)
colorNoJSON request body field — timeline event color (33 possible values)
timeline_event_typeYesJSON request body field — the timeline event type for this Scheduling operation
Behavior4/5

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

Annotations already indicate non-readonly and non-destructive. Description adds that it performs a partial update and returns the modified object, providing additional context beyond 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 description is concise, with the purpose front-loaded. A few sentences cover the key aspects, though could be slightly more compact.

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

Completeness3/5

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

While the description provides the API endpoint and required parameters, it lacks details about the return object structure or error handling. Given no output schema, more context could be useful.

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%, so the description does not need to add much. It lists required parameters but does not add meaning beyond 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?

The description clearly states it updates a timeline event partially, distinguishing it from create or delete siblings. It explicitly says 'Partially update a timeline event' and 'Use this to update an existing Scheduling records'.

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

Usage Guidelines3/5

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

The description explains when to use the tool (for partial updates) but does not explicitly state when not to use it or provide alternatives. It implies usage for partial updates only.

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