Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project User

create_project_user

Create a new user in a specified Procore project using project ID, email address, and last name. The API returns the created user with its new ID.

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. Pass the record's fields as top-level arguments — they are nested under "user" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted. Creates the project user and returns it with its new id (HTTP 201); calling it again creates another record. 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: project_id, email_address, last_name. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/projects/{project_id}/users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoJSON request body field — the Zip Code of the Project User
cityNoJSON request body field — the City in which the Project User resides
notesNoJSON request body field — the Notes (notes/keywords/tags) 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.
addressNoJSON request body field — the street Address 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
job_titleNoJSON request body field — the Job Title of the Project User
last_nameYesJSON request body field — the Last Name of the Project User
vendor_idNoJSON request body field — the Vendor 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
project_idYesURL path parameter — unique identifier for the project.
state_codeNoJSON request body field — the State Code of the Project User (ISO-3166 Alpha-2 format)
employee_idNoJSON request body field — the Employee ID of the Project User
is_employeeNoJSON request body field — the Employee status of the Project User
country_codeNoJSON request body field — the Country Code of the Project User (ISO-3166 Alpha-2 format)
mobile_phoneNoJSON request body field — the Mobile Phone number of the Project User
email_addressYesJSON request body field — the Email Address of the Project User
business_phoneNoJSON request body field — the Business Phone number of the Project User
email_signatureNoJSON request body field — the Email Signature of the Project User
permission_template_idNoJSON request body field — the Permission Template ID of the Project User
business_phone_extensionNoJSON request body field — the Business Phone Extension of the Project User
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
Behavior5/5

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

The description significantly extends beyond annotations by disclosing non-idempotency (calling again creates another record), HTTP 201 success, error payloads with common status codes (401, 403, 404), null key omission behavior, and ISO-3166 format requirements. This is rich behavioral context with no contradiction to the 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 well-organized with markdown headers and each section carries meaningful information. Minor repetition exists ('Creates a new user...' and 'Creates the project user...') but the structure is effective and not wasteful.

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?

For a tool with 24 parameters and no output schema, the description covers response status, error handling, field validation, defaults, and payload structure. It could be more explicit about the full return object shape, but the mention of returning the user with its new id and null key behavior provides adequate context.

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 coverage is 100%, so baseline is 3. The description adds value by specifying ISO-3166 format for country/state codes, explaining that request body fields are passed as top-level arguments despite being nested under 'user', and noting the project_id default behavior. This goes beyond simple schema descriptions.

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 'Creates a new user in the specified project' with a specific verb and resource. It also adds non-idempotency behavior ('calling it again creates another record') and confirms the scope, distinguishing it from sibling tools like update_project_user and list_project_users.

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 gives useful context: project_id defaults to procore_set_config, fields are passed as top-level arguments, and required parameters are listed. However, it does not explicitly contrast with alternatives like add_company_user_to_project or update_project_user, so it lacks explicit when/when-not guidance.

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