Skip to main content
Glama
TylerIlunga

Procore MCP Server

Company Folder And File Index

company_folder_and_file_index
Read-onlyIdempotent

List all folders and files in a Procore company document index. Query by folder, file type, date, or search to inspect company documents without modifying them.

Instructions

Return a list of all folders and files in the company. Use this when you already know which company folder and file index you want and need its full field set. company_id defaults to the value set by procore_set_config when omitted. Returns a single JSON object describing the company 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: company_id. Procore API (v2.0): Core > Documents. Endpoint: GET /rest/v2.0/companies/{company_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)
company_idYesURL path parameter — unique identifier for the company.
filters__searchNoQuery string parameter — returns item(s) matching the specified search query string.
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__is_in_recycle_binNoQuery string parameter — return item(s) that are in or not in the recycle bin
Behavior4/5

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

Annotations already declare readOnly and non-destructive, but the description adds valuable context: failure modes with HTTP status codes, common error scenarios (401, 403, 404), and the default behavior for company_id. This exceeds the structured information.

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 information-dense and well-structured, covering purpose, usage, return type, read-only behavior, errors, and API endpoint. It has slight redundancy but every sentence contributes useful details.

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 tool's complexity (13 params, no output schema), the description covers key aspects: main behavior, required params, default, error handling, and API reference. It could mention pagination behavior, but the schema's page/per_page parameters imply it.

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 100% of parameters, so baseline is 3. The description adds meaning for company_id by explaining it defaults to the procore_set_config value, which is not in the schema. Other parameters are adequately documented in the schema.

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 the tool returns a list of all folders and files in the company, which is a specific verb+resource+scope. It distinguishes from project-level siblings by explicitly mentioning 'in the company'.

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?

Provides a clear usage condition: use when you need the full field set of the company folder and file index. It implies not to use for project-level indices, though it does not explicitly name an alternative.

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