Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Timeline Event

delete_timeline_event
DestructiveIdempotent

Permanently remove a timeline event from a schedule. Use this action to delete a specified scheduling record that cannot be undone.

Instructions

Delete a timeline event from the schedule. Use this to permanently delete the specified Scheduling records. This cannot be undone. Permanently removes the specified Scheduling records. This action cannot be undone. Required parameters: company_id, project_id, schedule_id, timeline_event_id. Procore API (v2.0): Project Management > Scheduling. Endpoint: DELETE /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
Behavior3/5

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

Annotations already set destructiveHint=true. The description repeats 'cannot be undone' which is consistent but adds no new behavioral context beyond what annotations provide. It does not disclose additional traits like authorization needs or side effects.

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

Conciseness3/5

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

The description is somewhat repetitive, stating permanence twice. It front-loads the main action and includes endpoint info. Could be more concise.

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?

For a simple delete tool with full schema and annotations, the description covers the action and required parameters. It lacks guidance on outcomes or prerequisites, but overall adequate.

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% with each parameter described. The description merely lists required parameters without adding new meaning. Baseline 3 is appropriate.

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 tool deletes a timeline event from the schedule. It uses specific verb and resource. While it does not explicitly distinguish from sibling delete tools, the context of 'from the schedule' and the named resource make the purpose clear.

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 emphasizes permanence and irreversibility but does not guide when to use this tool versus other delete tools. There is no mention of preconditions, alternatives, or when not to use it.

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