Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Create Project

create_project

Create a new active project in a Procore account by providing company ID and project details.

Instructions

Create a new Project in a Procore account. The new project is active by default. #### Country and State codes The country_code and state_code parameter values must conform to the ISO-3166 Alpha-2 specification. See Working with Country Codes for additional information. #### Recommendation For accounts creating a significant number of projects (more than 300), schedule these operations during non-business hours (5 P.M PST - 7 A.M PST) to optimize efficienc... Use this to create a new Portfolio records in Procore. Creates a new Portfolio records and returns the created object on success (HTTP 201). Required parameters: company_id, project. Procore API: Core > Portfolio. Endpoint: POST /rest/v1.0/projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
company_idYesJSON request body field — the company identifier the project is associated with.
projectYesJSON request body field — the project for this Portfolio operation

Tool Definition Quality

A3.5/5.0
Behavior4/5

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

Adds value beyond annotations: active-by-default setting, return of created object on success (HTTP 201), and performance recommendation for large batches. No contradiction with annotations.

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?

Description is moderately sized with headers, but contains redundancy ('Portfolio records') and awkward phrasing, detracting from clarity.

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?

Covers essential context: active default, required params, country/state codes, return value. Lacks details on the full structure of the project object, but sufficient for a free-form nested parameter.

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?

Lists required parameters and provides ISO-3166 guidance for country/state codes inside the project object, adding meaning beyond the schema's minimal object description.

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 clearly states 'Create a new Project', but later mentions 'Portfolio records' inconsistently. It does not differentiate this tool from the sibling 'create_a_project'.

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

Usage Guidelines3/5

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

Provides implicit usage context (project active by default, country/state code requirements, scheduling recommendation for bulk), but no explicit guidance on when to use this vs. alternatives like 'bulk_create_project'.

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