Skip to main content
Glama
TylerIlunga

Procore MCP Server

Project Folder And File Index

project_folder_and_file_index
Read-onlyIdempotent

List all folders and files in a Procore project using project_id. Supports pagination and filters for document types, creators, and dates.

Instructions

Return a list of all folders and files in the project. Use this to read information about Documents from Procore. Returns a paginated JSON array of Documents. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API (v2.0): Core > Documents. Endpoint: GET /rest/v2.0/projects/{project_id}/documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
viewNoQuery string parameter — determines how much information to include in the response. `normal` is the default, `extended` provides additional data. The example below shows the `extended` response.
sortNoQuery string parameter — field to sort by. If the field is passed with a - (EX: -updated_at) it is sorted in reverse order
filters__created_by_idNoQuery string parameter — return item(s) created by the specified User IDs
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__document_typeNoQuery string parameter — return item(s) that are file or folder
filters__file_typeNoQuery string parameter — return item(s) that have the file extensions
filters__is_in_recycle_binNoQuery string parameter — return item(s) that are in or not in the recycle bin
filters__searchNoQuery string parameter — returns item(s) matching the specified search query string.
filters__folder_idNoQuery string parameter — returns the folder for a given id with all subfolders and subfiles up to a depth of 100. Depths greater than 100 will need multiple queries to get all children.
filters__custom_tag_idsNoQuery string parameter — return item(s) with specified custom tag IDs
filters__privateNoQuery string parameter — if true, returns only item(s) with a `private` status.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that the tool returns a paginated JSON array and mentions pagination controls, but does not disclose significant behavioral traits beyond what annotations provide.

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, consisting of two efficient sentences. It is front-loaded with the primary purpose and includes essential details (pagination, required parameter, API endpoint) without superfluous information.

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 absence of an output schema, the description adequately explains that the response is a paginated JSON array of Documents and notes pagination metadata. It also provides the API version and endpoint. However, it does not elaborate on the Document object structure or the behavior of filters, which are well-documented in the schema 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 the input schema already fully describes all 15 parameters with detailed descriptions. The description only minimally adds context about pagination ('Use page and per_page to control pagination'), which is already covered in the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Return' and the resource 'all folders and files', distinguishing it as a read-only listing tool. It mentions the context of Procore Documents and the API endpoint, but does not explicitly differentiate from sibling tools like 'list_project_folders_and_files'.

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

Usage Guidelines3/5

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

The description indicates to use this tool for reading information about Documents, but does not provide guidance on when not to use it or suggest alternatives among the many sibling listing tools. The usage context is implied rather than explicit.

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