Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Company User

create_company_user_v1_3

Create a new user within a specified Procore company. Requires company ID, last name, and email address to complete.

Instructions

Create a new User in the specified Company. #### Uploading 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. #### 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. Pass the record's fields as top-level arguments — they are nested under "user" in the request payload for you. company_id defaults to the value set by procore_set_config when omitted. Creates the company 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: company_id, last_name, email_address. Procore API (v1.3): Core > Directory. Endpoint: POST /rest/v1.3/companies/{company_id}/users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoJSON request body field — the Zip code of the Company User
cityNoJSON request body field — the City of the Company User
notesNoJSON request body field — the Notes (notes, keywords, tags) of the Company User
avatarNoJSON request body field — the Avatar of the Company User. 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 Address of the Company User
initialsNoJSON request body field — the Initials of the Company User
is_activeNoJSON request body field — the Active status of the Company User
job_titleNoJSON request body field — the Job Title of the Company User
last_nameYesJSON request body field — the Last Name of the Company User
origin_idNoJSON request body field — the Origin ID of the Company User
vendor_idNoJSON request body field — the ID of the Vendor of the Company User
company_idYesURL path parameter — unique identifier for the company.
fax_numberNoJSON request body field — the Fax Number of the Company User
first_nameNoJSON request body field — the First Name of the Company User
state_codeNoJSON request body field — the State Code of the Company User (ISO-3166 Alpha-2 format)
bid_contactNoJSON request body field — sets the user as a bid contact for the vendor it is associated with. `vendor_id` must also be provided for this to be set.
employee_idNoJSON request body field — the ID of the Employee of the Company User when `user[is_employee]` is set to `true`
is_employeeNoJSON request body field — the Employee status of the Company User
origin_dataNoJSON request body field — the Origin Data of the Company User
country_codeNoJSON request body field — the Country Code of the Company User (ISO-3166 Alpha-2 format)
mobile_phoneNoJSON request body field — the Mobile Phone of the Company User
email_addressYesJSON request body field — the Email Address of the Company User. Update requests including this parameter will be rejected unless the requesting user has Directory Admin permissions
business_phoneNoJSON request body field — the Business Phone of the Company User
email_signatureNoJSON request body field — the Email Signature of the Company User
work_classification_idNoJSON request body field — the ID of the Work Classification for the Company User
business_phone_extensionNoJSON request body field — the Business Phone Extension of the Company User
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
company_permission_template_idNoJSON request body field — the ID of the Company Permission Template for the Company User. Requests including this parameter will be rejected unless the requesting user has Directory Admin permissions
default_permission_template_idNoJSON request body field — the ID of the default Permission Template for the Company User. Requests including this parameter will be rejected unless the requesting user has Directory Admin permissions
Behavior5/5

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

The description goes well beyond the annotations by disclosing concrete behavioral traits: non-idempotency ('calling it again creates another record'), the HTTP 201 response with the new id, common error statuses (401/403/404), the multipart constraint for avatar upload, and ISO-3166 validation for country/state codes. All statements align with the annotations (readOnly=false, idempotent=false, destructive=false), showing no contradiction.

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 long but well-structured with markdown headers for avatar upload, ISO codes, and general behavior. It packs in necessary operational details (required params, default, non-idempotency, error handling) without filler. While it could be trimmed slightly, the density is justified given the tool's 29 parameters and non-trivial request encoding.

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, the description covers the essential aspects: purpose, endpoint, required fields, request encoding, non-idempotency, error responses, and special upload requirements. It lacks an explicit statement about required permissions (beyond the 403 error mention) and does not describe the full response structure, but the annotations and schema fill most gaps. No output schema exists, so the description's disclosure of returning the new id is sufficient.

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% with each parameter having a description, so the baseline is 3. The description enhances this by explaining the top-level vs. nested request payload relationship, specifying that company_id is a URL path parameter, and adding a link for ISO country code details. These additions give the agent a better mental model of how to construct arguments, meriting a 4.

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 opens with a clear, specific verb and resource: 'Create a new User in the specified Company.' It further distinguishes itself from siblings by explicitly noting the non-idempotent nature ('calling it again creates another record') and by giving the exact endpoint (POST /rest/v1.3/companies/{company_id}/users), which separates it from update, list, and show variants.

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 provides practical guidance: lists required parameters, explains that fields are passed as top-level arguments despite being nested under 'user' in the payload, documents the company_id default from procore_set_config, and details the avatar multipart/form-data requirement. However, it does not explicitly name alternative tools for updating or listing users, relying on the verb 'Create' to imply when to use it.

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