Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Schedules

list_schedules
Read-onlyIdempotent

Retrieve a paginated list of schedules for a project. Filter results by name, type, active status, or update time to find specific records.

Instructions

List all schedules in a project. Use the Show Project API when you need the project time zone to interpret UTC timestamps or values expressed in project time. 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. Procore API (v2.0): Project Management > Scheduling. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/schedules

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company
project_idYesURL path parameter — unique identifier for the project
filters__schedule_idNoQuery string parameter — filter schedules by schedule_id
filters__schedule_nameNoQuery string parameter — filter schedules by name
filters__schedule_typeNoQuery string parameter — filter schedules by type. Values must exactly match a valid schedule type (case-sensitive)
filters__is_activeNoQuery string parameter — filter schedules by active status
filters__updated_at__gtNoQuery string parameter — filter for schedules updated after this timestamp (ISO 8601 instant)
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?

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), description adds pagination behavior, required parameters, and endpoint info. No contradiction. Slight deduction as annotations already cover safety profile.

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?

Concise at 4 sentences, front-loaded with purpose. Efficient but could be slightly more streamlined without losing essential info.

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?

Describes return as paginated JSON array with metadata. No output schema, but description covers key outputs. For a listing tool with rich schema, this is 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?

Input schema has 100% description coverage, so baseline is 3. Description mentions required parameters but adds minimal extra meaning beyond schema. No need for additional param details.

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?

Clearly states 'List all schedules in a project' with specific verbs and resource. Differentiates from sibling tools like 'Show Project API' by specifying context.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool (paginated overview, find IDs, filter) and when to use alternatives (Show Project API for time zone). Provides clear usage context.

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