Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Projects

list_projects
Read-onlyIdempotent

Retrieve a paginated list of active projects for a company. Filter by status, name, ID, or custom fields. Returns projects accessible to the authenticated user.

Instructions

Return a list of active Projects. If the authenticated user has full company admin permissions the request will return all of the projects in the company. If the user does not have full company admin permissions, the request will only return the projects that the user has been added to. The default pagination is 100 projects per page. The max page size is 300 projects due to the size of the data in the response. See [Filtering on List Actions](https://developers.procore.com/documentation/fi... Use this to enumerate Portfolio records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Portfolio records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API (v1.1): Core > Portfolio. Endpoint: GET /rest/v1.1/projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesQuery string parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__by_statusNoQuery string parameter — filters on project status. Must be one of Active, Inactive, or All.
filters__nameNoQuery string parameter — filters projects to those matching the given string.
filters__project_numberNoQuery string parameter — filters on project number.
filters__created_atNoQuery string parameter — return item(s) created 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 `YYYY-MM-...
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__origin_idNoQuery string parameter — origin ID. Returns item(s) with the specified Origin ID.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__syncedNoQuery string parameter — if true, returns only item(s) with a `synced` status.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor ID.
filters__is_demoNoQuery string parameter — filters on project is_demo attribute, which indicates whether project is for demonstration purposes.
filters__custom_fieldsNoQuery string parameter — jSON object returns project with matching custom_field_values
filters__templateNoQuery string parameter — filters on project template attribute, which indicates whether project is a template
filters__by_owner_typeNoQuery string parameter — return item(s) with the specified project owner type ID(s).
filters__by_departmentNoQuery string parameter — return item(s) with the specified department ID(s).
filters__by_regionNoQuery string parameter — return item(s) with the specified project region ID(s).
filters__by_officeNoQuery string parameter — return item(s) with the specified office ID(s).
filters__by_programNoQuery string parameter — return item(s) with the specified project program ID(s).
filters__by_stageNoQuery string parameter — return item(s) with the specified project stage ID(s).
filters__by_typeNoQuery string parameter — return item(s) with the specified project type ID(s).
filters__by_bid_typeNoQuery string parameter — return item(s) with the specified project bid type ID(s).
viewNoQuery string parameter — the view determines which fields are returned. 'ids' return only id as an Integer (it additionally influences 'per_page' value to be strictly 200000), 'compact' returns only id and name, 'normal' r...
sortNoQuery string parameter — return items with the specified sort.
Behavior4/5

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

Annotations already indicate readOnly and idempotent. The description adds valuable behavioral details: admin vs non-admin result sets, pagination limits (100 default, 300 max), and filtering capabilities. No contradictions with annotations.

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

Conciseness2/5

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

The description is verbose and includes a broken markdown link ('See [Filtering on List Actions]'). It repeats endpoint and portfolio info. While informative, it could be more concise and structured.

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 25 parameters and no output schema, the description covers purpose, permissions, pagination, filtering, and endpoint details. It is fairly complete, though the long list of filters could be summarized more efficiently. An output schema would reduce this score.

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 adds high-level usage hints (e.g., 'Use page and per_page to control pagination') but does not significantly augment parameter meanings beyond the schema. 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 the tool returns a list of active Projects, distinguishes behavior based on admin permissions, and specifies pagination and filtering capabilities. It is specific and differentiates from many sibling list tools.

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 usage context: enumerate Portfolio records, find IDs, or filter by query parameters. It does not explicitly mention when not to use or alternatives, but the guidance is sufficient for appropriate invocation.

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