Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Company User

create_company_user_v1_0

Create a new user in a Procore company directory. Provide company ID, last name, and email address to add a directory record.

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. 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: company_id, last_name, email_address. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesQuery string parameter — unique identifier for the company.
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
first_nameNoJSON request body field — the First Name of the Company User
last_nameYesJSON request body field — the Last Name of the Company User
job_titleNoJSON request body field — the Job Title of the Company User
addressNoJSON request body field — the Address of the Company User
cityNoJSON request body field — the City of the Company User
zipNoJSON request body field — the Zip code of the Company User
business_phoneNoJSON request body field — the Business Phone of the Company User
business_phone_extensionNoJSON request body field — the Business Phone Extension of the Company User
mobile_phoneNoJSON request body field — the Mobile Phone of the Company User
fax_numberNoJSON request body field — the Fax Number 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
email_signatureNoJSON request body field — the Email Signature of the Company User
is_activeNoJSON request body field — the Active status of the Company User
is_employeeNoJSON request body field — the Employee status of the Company User
employee_idNoJSON request body field — the ID of the Employee of the Company User when `user[is_employee]` is set to `true`
notesNoJSON request body field — the Notes (notes, keywords, tags) of the Company User
country_codeNoJSON request body field — the Country Code of the Company User (ISO-3166 Alpha-2 format)
state_codeNoJSON request body field — the State Code of the Company User (ISO-3166 Alpha-2 format)
initialsNoJSON request body field — the Initials of the Company User
origin_idNoJSON request body field — the Origin ID of the Company User
origin_dataNoJSON request body field — the Origin Data of the Company User
vendor_idNoJSON request body field — the ID of the Vendor of the Company User
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
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
work_classification_idNoJSON request body field — the ID of the Work Classification for 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.
Behavior4/5

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

Annotations are minimal (no readOnly, destructive, idempotent hints). The description adds value by detailing avatar upload as multipart/form-data, country/state code standards (ISO-3166), and return behavior (HTTP 201 with created object). This compensates for the sparse annotations without contradicting them.

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 front-loaded with the core purpose and uses markdown headers to organize special cases. It is moderately concise, though the repetition of 'create a new Directory records' twice slightly reduces efficiency.

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?

With 28 parameters and no output schema, the description only highlights two special cases (avatar and country codes) and the required parameters. While the schema covers field details, a more complete description would mention permission requirements (noted in schema) or integration details for a complex tool.

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 description coverage is 100%, so the schema already explains all parameters. The description adds extra context for avatar upload and country/state codes, but this is only a small addition beyond the parameter descriptions, justifying the baseline score.

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 'Create a new User in the specified Company' and references 'Directory records.' The verb-resource pair is specific, but it does not differentiate between this v1.0 and the sibling v1.3 version, leaving ambiguity about which version to choose.

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 implicitly states 'Use this to create a new Directory records in Procore' but offers no guidance on when not to use it or alternatives like bulk creation or project-specific user tools. It lists required parameters but lacks explicit exclusions or context for selection among siblings.

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