Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Calendar Items

list_calendar_items
Read-onlyIdempotent

Retrieve paginated calendar items for a project. Use filters and sorting to find schedule records by date, assignee, or query.

Instructions

Returns all Calendar Items for a given project. Use this to enumerate Schedule (Legacy) records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Schedule (Legacy) records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Schedule (Legacy). Endpoint: GET /rest/v1.0/projects/{project_id}/schedule/calendar_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
viewNoQuery string parameter — the view to use when serializing Calendar Item data. The ids_only view returns an array of Calendar Item IDs. The total_count_only view returns total count of Calendar Items.
start_dateNoQuery string parameter — calendar Items that occur after this date
finish_dateNoQuery string parameter — calendar Items that occur before this date
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__queryNoQuery string parameter — return item(s) containing search query
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
filters__assigned_idNoQuery string parameter — returns task(s) with specified assignee(s)
filters__dateNoQuery string parameter — returns task(s) existing on the specified ISO 8601 datetime
sortNoQuery string parameter — return item(s) with the specified sort. Prepend "-" to specify descending order.
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that the tool returns a paginated JSON array with pagination metadata, and specifies the required project_id and endpoint, providing useful behavioral 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?

Description is relatively concise with three main sentences, though it includes some redundancy (e.g., repeating 'paginated JSON array'). 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.

Completeness4/5

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

Given 11 parameters and no output schema, the description covers the key aspects: what is returned, pagination, required parameter, and API reference. It does not cover rate limits or output format specifics, but the schema fills in details for parameters.

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 baseline is 3. The description mentions required project_id and pagination (page, per_page) but does not detail all parameters. This adds marginal context but is not needed 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?

Describes specific verb 'Returns' and resource 'Calendar Items' for a given project, clarifies it pertains to Schedule (Legacy) records, and distinguishes from siblings like 'list_calendar_events' by naming the legacy schedule and providing the endpoint.

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?

Explicitly states when to use—'when you need a paginated overview, to find IDs, or to filter by query parameters.' Lacks explicit when-not-to-use or alternatives, but the context is clear given the sibling listing 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