Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Folders And Files

list_project_folders_and_files
Read-onlyIdempotent

List all folders and files in a Procore project's root folder. Filter results by excluding folders or files, showing only the latest version, and paginate to manage document enumeration.

Instructions

Returns a list of folders and files for a specified project. Note: this operation will return all of the folders and files within the root folder of that project's document structure. For any folders that are nested more deeply an empty array [] will be returned. Use this to enumerate Documents when you need a paginated overview, to find IDs, or to filter by query parameters. 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: Core > Documents. Endpoint: GET /rest/v1.0/folders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
exclude_foldersNoQuery string parameter — exclude child folders from results. Must be either true or false.
exclude_filesNoQuery string parameter — exclude child files from results. Must be either true or false.
show_latest_file_version_onlyNoQuery string parameter — show only the latest file version. Must be either true or false.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber 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 the tool as read-only, idempotent, and non-destructive. The description adds behavioral context (root-only listing, nested folders return empty array) but lacks details on error handling or authorization requirements.

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?

The description is concise (6 sentences) and front-loaded with the main purpose. It efficiently covers key points without 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 no output schema, the description adequately describes the response (paginated JSON array of Documents) and covers usage, pagination, and API endpoint. Missing error handling but otherwise complete for a list tool.

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 descriptions for all parameters. The description only reiterates that project_id is required and page/per_page control pagination, adding marginal value beyond the schema.

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 tool returns a list of folders and files for a specified project, and specifies it operates on the root folder only. It distinguishes itself from sibling tools by scoping to a project, but does not explicitly differentiate from similar tools like 'company_folder_and_file_index'.

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 provides concrete use cases (enumerate documents, find IDs, filter) and mentions pagination control, but does not explicitly state when not to use it or name alternative tools for different scopes.

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