Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project User

create_project_user

Add a new user to a Procore project by providing their email, last name, and project ID. Includes optional fields for contact details and permissions.

Instructions

Creates a new user in the specified project. #### 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. #### Created Response For null values, the key won't be returned. Use this to create a new Directory records in Procore. Creates a new Directory records and returns the created object on success (HTTP 201). Required parameters: project_id, email_address, last_name. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/projects/{project_id}/users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
addressNoJSON request body field — the street Address of the Project User
avatarNoJSON request body field — project User Avatar. To upload avatar you must upload whole payload as `multipart/form-data` content-type and specify each parameter as form-data together with `user[avatar]` as file.
business_phoneNoJSON request body field — the Business Phone number of the Project User
business_phone_extensionNoJSON request body field — the Business Phone Extension of the Project User
cityNoJSON request body field — the City in which the Project User resides
country_codeNoJSON request body field — the Country Code of the Project User (ISO-3166 Alpha-2 format)
email_addressYesJSON request body field — the Email Address of the Project User
email_signatureNoJSON request body field — the Email Signature of the Project User
employee_idNoJSON request body field — the Employee ID of the Project User
fax_numberNoJSON request body field — the Fax Number of the Project User
first_nameNoJSON request body field — the First Name of the Project User
initialsNoJSON request body field — the Initials of the Project User
is_activeNoJSON request body field — the Active status of the Project User
is_employeeNoJSON request body field — the Employee status of the Project User
job_titleNoJSON request body field — the Job Title of the Project User
last_nameYesJSON request body field — the Last Name of the Project User
mobile_phoneNoJSON request body field — the Mobile Phone number of the Project User
notesNoJSON request body field — the Notes (notes/keywords/tags) of the Project User
permission_template_idNoJSON request body field — the Permission Template ID of the Project User
state_codeNoJSON request body field — the State Code of the Project User (ISO-3166 Alpha-2 format)
vendor_idNoJSON request body field — the Vendor ID of the Project User
zipNoJSON request body field — the Zip Code of the Project User
Behavior4/5

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

Annotations indicate mutation (readOnlyHint=false) and non-destructive nature (destructiveHint=false). The description adds that the tool returns the created object on success (HTTP 201) and that null values result in omitted keys. It also clarifies ISO-3166 code format, providing behavioral context beyond annotations.

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 structured with clear sections for country/state codes and response behavior. It front-loads the main action. Though slightly verbose and redundant ('Creates a new user... Creates a new Directory records'), it remains efficient for the amount of detail.

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 lack of output schema, the description explains return behavior (created object, null key omission) and lists required parameters and endpoint. It covers essential context for a creation tool, though further details on optional parameters rely on the schema.

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 coverage is 100% with all 24 parameters described. The description only adds that country_code and state_code must be ISO-3166 Alpha-2, and lists required parameters which are already in the schema. No additional parameter meaning is provided beyond what the schema already conveys.

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 verb (Creates), resource (user), and scope (in the specified project). It distinguishes from sibling tools like 'add_company_user_to_project' by implying this creates a new user rather than adding an existing one. The mention of 'new Directory records' further clarifies the purpose.

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?

The description provides required parameters and endpoint but lacks explicit guidance on when to use this tool versus alternatives like 'add_company_user_to_project' or 'create_company_user_v1_0'. Usage is implied but no when-not-to-use or exclusions are stated.

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