Skip to main content
Glama
TylerIlunga

Procore MCP Server

Company Folder And File Index

company_folder_and_file_index
Read-onlyIdempotent

Retrieve a paginated list of all folders and files in a Procore company. Filter by document type, creator, date, or search to find specific documents.

Instructions

Return a list of all folders and files in the company. 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: company_id. Procore API (v2.0): Core > Documents. Endpoint: GET /rest/v2.0/companies/{company_id}/documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
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.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior4/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 value by specifying pagination behavior (page and per_page control, response includes metadata) and the API endpoint. It does not detail other behaviors like rate limits or error handling, but the annotation coverage lowers the burden.

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, with only a few sentences that are front-loaded with the core purpose. Every sentence earns its place without unnecessary detail.

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

Completeness5/5

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

Given the 13 parameters covered by schema and no output schema, the description adequately explains the tool's purpose, required parameter, pagination, and response structure (paginated JSON array with metadata). It is complete for a list endpoint.

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 baseline is 3. The description mentions that company_id is required and page/per_page control pagination, but these are already evident from the schema. It adds minimal extra meaning beyond what the schema provides.

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 that the tool returns a list of all folders and files in the company, specifying the verb 'Return' and the resource 'folders and files' / 'Documents'. It distinguishes from the sibling 'project_folder_and_file_index' by explicitly mentioning 'in the company' at the start.

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 advises to 'Use this to read information about Documents from Procore', providing a clear context. However, it does not explicitly exclude or mention alternatives like 'list_company_folders_and_files' when multiple similar list tools exist.

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