Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Activities

list_activities
Read-onlyIdempotent

Retrieve all activities in a Procore schedule. Filter by activity ID, name, critical status, or update timestamp, and paginate results using page and per_page parameters.

Instructions

List all activities in a schedule. 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, schedule_id. Procore API (v2.0): Project Management > Scheduling. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/schedules/{schedule_id}/activities

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__activity_idNoQuery string parameter — filter activities by activity_id
filters__activity_nameNoQuery string parameter — filter activities by name
filters__is_criticalNoQuery string parameter — filter activities by critical path status in read only project schedule
filters__updated_at__gtNoQuery string parameter — filter for activities updated after this timestamp (ISO 8601)
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
Behavior3/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds that the tool returns a paginated JSON array of Scheduling records with pagination metadata, which is useful but not extensive. No additional behavioral details like authentication or rate limits are disclosed.

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

Conciseness5/5

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

The description is concise and well-structured: it starts with the main purpose, then usage guidance, return type, pagination control, required parameters, and API reference. Every sentence adds value with no redundancy.

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 the tool has 10 parameters and no output schema, the description covers the essential aspects: what it does, when to use alternatives, the return format (paginated array of Scheduling records), pagination metadata, required parameters, and the API endpoint. It is sufficient for an agent to understand the tool's purpose and basic behavior.

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 the schema already documents all parameters with descriptions. The description highlights the required parameters and mentions page/per_page for pagination, but does not add significant meaning beyond what the schema provides. Baseline 3 is appropriate.

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 activities in a schedule' with a specific verb and resource. It differentiates from siblings by explicitly mentioning when to use the Show Project API for time zone interpretation and when to use this tool for paginated overviews, ID finding, or filtering.

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 provides clear context for use: 'Use this to enumerate Scheduling records when you need a paginated overview, to find IDs, or to filter by query parameters' and contrasts with the Show Project API for time zone needs. However, it does not explicitly state when not to use this tool or list alternatives beyond the one mentioned.

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