Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company User

update_company_user
Idempotent

Modify a company user's profile in Procore by sending only changed fields—name, contact details, job title, or permission template—while leaving other values intact.

Instructions

Update the specified User. #### 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. Send only the fields you intend to change; omitted fields keep their current values. 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, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified company user on success. 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, id, last_name, email_address. Procore API (v1.3): Core > Directory. Endpoint: PATCH /rest/v1.3/companies/{company_id}/users/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Directory resource
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)
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
add_to_new_projectsNoJSON request body field — whether or not this user is added to all new projects. 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
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?

Beyond the annotations (readOnlyHint=false, etc.), the description discloses PATCH-style partial updates, the avatar multipart requirement, ISO-3166 code constraints, company_id defaulting behavior, return value, and common error statuses (401, 403, 404). This is rich behavioral context.

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 clear headings and each sentence providing needed detail. It front-loads the core purpose and systematically covers special cases, making it dense yet organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description explains return values ('Returns the modified company user') and error payloads. It also covers prerequisites, special encoding, config defaults, and required parameters, making it comprehensive for a complex tool.

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?

Even though schema coverage is 100%, the description adds meaning by explaining the 'user' nesting, special multipart handling for avatar, ISO code format requirements, company_id defaulting, and the need to resolve id via list tool. It does not repeat each parameter but adds contextual value.

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 the tool's function ('Update the specified User') with a specific verb and resource (Company User). However, it does not explicitly differentiate from sibling tools like create_company_user or update_project_user, though the name and return value clarify the scope.

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?

Provides clear usage context: partial update semantics ('Send only the fields you intend to change'), prerequisite resolution ('resolve it with the matching list tool first'), and configuration default for company_id. It does not explicitly exclude alternatives, but the context is sufficient.

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