Skip to main content
Glama
TylerIlunga

Procore MCP Server

project_folder_and_file_index

Retrieve and organize project documents and folders from Procore. Filter, sort, and search files to manage construction documentation efficiently.

Instructions

Project Folder and File index. [Core/Documents] GET /rest/v1.0/projects/{project_id}/documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
viewNoDetermines how much information to include in the response. `normal` is the default, `extended` provides additional data. The example below shows the `extended` response.
sortNoField to sort by. If the field is passed with a - (EX: -updated_at) it is sorted in reverse order
filters__created_by_idNoReturn item(s) created by the specified User IDs
filters__created_atNoReturn 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_atNoReturn 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_typeNoReturn item(s) that are file or folder
filters__file_typeNoReturn item(s) that have the file extensions
filters__is_in_recycle_binNoReturn item(s) that are in or not in the recycle bin
filters__searchNoReturn item(s) that contain string in document name and file description
filters__folder_idNoReturns 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_idsNoReturn item(s) with specified custom tag IDs
filters__privateNoIf true, returns only item(s) with a `private` status.
pageNoPage
per_pageNoElements per page
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'GET', implying a read-only operation, but doesn't disclose behavioral traits like pagination (implied by 'page' and 'per_page' parameters), rate limits, authentication needs, or response format. The description lacks critical context for safe and effective use, leaving gaps in transparency.

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 with two parts: a brief title-like phrase and a REST endpoint. It's front-loaded but could be more structured (e.g., separating purpose from technical details). There's no wasted text, but it's under-specified rather than optimally concise, slightly reducing effectiveness.

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

Completeness2/5

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

Given the complexity (15 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's behavior, output format, or error handling. For a read operation with extensive filtering and pagination, more context is needed to guide the agent effectively, making it inadequate for the tool's richness.

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 description coverage is 100%, so the schema fully documents all 15 parameters. The description adds no parameter semantics beyond the schema—it doesn't explain how parameters interact (e.g., filtering combinations) or provide examples. Baseline score of 3 is appropriate as the schema does the heavy lifting, but the description doesn't compensate with additional insights.

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

Purpose3/5

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

The description 'Project Folder and File index. [Core/Documents] GET /rest/v1.0/projects/{project_id}/documents' indicates it retrieves documents for a project, but it's vague. It mentions 'index' and 'GET', implying listing, but doesn't specify if it lists folders/files, filters, or paginates. It distinguishes from siblings like 'company_folder_and_file_index' by specifying 'project', but the purpose isn't clearly articulated beyond a REST endpoint reference.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives is provided. The description includes a REST path but doesn't explain context, prerequisites, or comparisons to other tools (e.g., 'project_folder_and_file_index_v2_0' or other listing tools). Usage is implied by the endpoint, but explicit guidelines are absent.

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