Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Folder

create_project_folder

Create a new folder in a Procore project to organize documents. Specify project ID and folder name; optionally set parent folder, tracking, or permissions.

Instructions

Create a new folder in the specified project. Use this to create a new Documents in Procore. Creates a new Documents and returns the created object on success (HTTP 201). Required parameters: project_id, name. Procore API: Core > Documents. Endpoint: POST /rest/v1.0/folders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
parent_idNoJSON request body field — the ID of the parent folder to create the folder in. If not set the folder will be created under the root folder.
nameYesJSON request body field — the Name of the folder
is_trackedNoJSON request body field — status if a folder should be tracked (true/false)
explicit_permissionsNoJSON request body field — set folder to private (true/false)
custom_field_%{custom_field_definition_id}NoJSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
Behavior2/5

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds that it returns HTTP 201 on success, but doesn't detail side effects, authorization needs, rate limits, or other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively short but contains redundancy and a confusing phrase ('create a new Documents'). It could be more streamlined and clear.

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?

The description covers the return status but omits information about optional parameters (parent_id, is_tracked, etc.) and potential errors. With 6 parameters and no output schema, more detail would be helpful.

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?

With 100% schema description coverage, the baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions, merely stating that project_id and name are required.

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 action (create) and resource (folder) with required parameters. However, the phrasing 'create a new Documents' is slightly confusing, and it doesn't explicitly differentiate from sibling tools like 'create_project_file' or 'create_company_folder'.

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?

The description provides no guidance on when to use this tool versus alternatives. It only lists required parameters without any contextual decision-making help or exclusions.

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