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 its project ID. Get a paginated, filterable index of documents with metadata, including sorting and search capabilities.

Instructions

Return a list of all folders and files in the project. Use this when you already know which project folder and file index you want and need its full field set. project_id defaults to the value set by procore_set_config when omitted. Returns a single JSON object describing the project folder and file index. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id. Procore API (v2.0): Core > Documents. Endpoint: GET /rest/v2.0/projects/{project_id}/documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — field to sort by. If the field is passed with a - (EX: -updated_at) it is sorted in reverse order
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.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.
filters__searchNoQuery string parameter — returns item(s) matching the specified search query string.
filters__privateNoQuery string parameter — if true, returns only item(s) with a `private` status.
filters__file_typeNoQuery string parameter — return item(s) that have the file extensions
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__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__created_by_idNoQuery string parameter — return item(s) created by the specified User IDs
filters__document_typeNoQuery string parameter — return item(s) that are file or folder
filters__custom_tag_idsNoQuery string parameter — return item(s) with specified custom tag IDs
filters__is_in_recycle_binNoQuery string parameter — return item(s) that are in or not in the recycle bin
Behavior5/5

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

Despite strong annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds valuable behavioral context: project_id defaults to procore_set_config, failure modes with HTTP status codes (401/403/404), and explicit read-only assurance. This goes well beyond the annotations.

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?

Every sentence contributes: purpose, usage scenario, default behavior, return type, safety, error handling, required params, and API endpoint. It's dense but well-organized and front-loaded with the primary action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is vague about return value structure. 'Returns a single JSON object describing the project folder and file index' does not explain what fields or nested structure to expect, and it doesn't mention pagination behavior. Error handling and defaults are good, but the output description is insufficient for a tool with 15 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 15 parameters comprehensively. The description adds one critical nuance not in the schema: project_id defaults to the value set by procore_set_config when omitted, which is essential for correct invocation. This elevates it above the baseline.

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 'Return a list of all folders and files in the project,' providing a specific verb and resource. However, it does not explicitly distinguish this tool from the sibling list_project_folders_and_files or the company-scoped variant, so it falls short of full sibling differentiation.

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?

It provides clear context: 'Use this when you already know which project folder and file index you want and need its full field set.' This implies the appropriate scenario but does not explicitly state when not to use alternatives or name them.

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