Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company User

update_company_user

Updates an existing company user's directory record by modifying specified fields such as name, contact info, and permissions. Requires company_id, user id, last name, and email address.

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. Use this to update an existing Directory records (only the supplied fields are changed). Updates the specified Directory records and returns the modified object on success. 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
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — unique identifier of the Directory resource
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.
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
Behavior4/5

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

Adds important behavioral details beyond annotations: avatar upload requires multipart/form-data, country/state codes must be ISO-3166 Alpha-2, returns the modified object. Annotations already indicate not read-only and not destructive, so description effectively supplements 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?

Front-loaded with purpose, then structured sections for avatar and country codes. Includes endpoint and required parameters. Slightly redundant but overall 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?

Covers key behavioral details (avatar, country codes, partial update, return value) given 30 parameters and no output schema. Lacks information about permissions or error cases, but sufficient for most use cases.

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 has 100% coverage, so baseline is 3. Description adds valuable context for avatar upload mechanism and country/state code format, but does not explain other parameters beyond what schema describes.

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?

Description clearly states 'Update the specified User' and 'Updates the specified Directory records', with specific verb and resource. It distinguishes from siblings like create_company_user_v1_3 by focusing on update operations.

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?

Provides usage context ('Use this to update an existing Directory records') and notes partial updates ('only the supplied fields are changed'), but does not mention when to avoid this tool or suggest alternatives, leaving some ambiguity.

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