Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Timeline Events

list_timeline_events
Read-onlyIdempotent

Retrieve a paginated list of timeline events for a schedule. Use filters by ID, name, or delete status to find specific records.

Instructions

List all timeline events in a schedule. Use this to enumerate Scheduling records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Scheduling records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, schedule_id. Procore API (v2.0): Project Management > Scheduling. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/schedules/{schedule_id}/timeline_events

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
filters__timeline_event_idNoQuery string parameter — filter timeline events by timeline_event_id
filters__timeline_event_nameNoQuery string parameter — filter timeline events by timeline_event_name
filters__source_activity_deletedNoQuery string parameter — filter timeline events by source activity deleted status
sortNoQuery string parameter — sort by supported fields. Accepts comma separated values to sort by multiple fields. Order is ascending by default, prefix field with '-' for descending
pageNoQuery string parameter — the page number to retrieve
per_pageNoQuery string parameter — number of records per page
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral details: returns paginated JSON array with pagination metadata, and lists required parameters. No contradiction.

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 front-loaded with the main action, followed by use cases, return info, pagination guidance, required params, and API endpoint. Every sentence adds value, though it could be slightly more concise.

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

Completeness4/5

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

Given no output schema, the description adequately states returns a paginated JSON array with metadata. It covers purpose, usage, required params, pagination, and API reference. Sufficient for a list operation.

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 detailed descriptions for all parameters. The description reiterates required parameters and pagination (page, per_page) but does not add significant new 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 'List all timeline events in a schedule' and provides specific use cases (enumerate records, find IDs, filter by query). It distinguishes itself from sibling tools like create_timeline_event, delete_timeline_event, and get_timeline_event_by_id.

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?

The description explicitly says when to use this tool: for paginated overview, finding IDs, or filtering. It implies alternatives (e.g., get_timeline_event_by_id for single record) but does not explicitly exclude other 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