Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project User

update_project_user

Update an existing project user's directory record. Modify only the fields that need to change, such as name, contact info, or activation status.

Instructions

Updates the specified project user. 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. For OK responses with null values, the key will not be returned. Note: The is_active parameter value requires a boolean value to be passed in. Setting this parameter to false deactivates the user. If you have deactivated a user by setting is_active to false an... 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: project_id, id. Procore API: Core > Directory. Endpoint: PATCH /rest/v1.0/projects/{project_id}/users/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
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.
abbreviated_nameNoJSON request body field — the Initials of the Project User
addressNoJSON request body field — the street Address 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.
business_phoneNoJSON request body field — the Business Phone number of the Project User
business_phone_extensionNoJSON request body field — the Business Phone Extension of the Project User
cityNoJSON request body field — the City in which the Project User resides
country_codeNoJSON request body field — the Country Code of the Project User (ISO-3166 Alpha-2 format)
email_addressNoJSON request body field — the Email Address of the Project User
email_signatureNoJSON request body field — the Email Signature of the Project User
employee_idNoJSON request body field — the Employee 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
is_activeNoJSON request body field — the Active status of the Project User
is_employeeNoJSON request body field — the Employee status of the Project User
job_titleNoJSON request body field — the Job Title of the Project User
last_nameNoJSON request body field — the Last Name of the Project User
mobile_phoneNoJSON request body field — the Mobile Phone number of the Project User
notesNoJSON request body field — the Notes (notes/keywords/tags) of the Project User
state_codeNoJSON request body field — the State Code of the Project User (ISO-3166 Alpha-2 format)
vendor_idNoJSON request body field — the Vendor ID of the Project User
zipNoJSON request body field — the Zip Code of the Project User
Behavior4/5

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

Annotations indicate a write operation (readOnlyHint false) and non-destructive (destructiveHint false). The description adds valuable details: null value keys omitted in OK response, is_active boolean deactivation behavior, and endpoint info. This exceeds annotation-provided context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is repetitious (e.g., 'Updates the specified project user' appears twice) and includes extraneous API details (endpoint, Procore API section). It lacks a clear structure, making it harder to parse quickly.

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 full schema coverage and no output schema, the description covers parameter constraints and partial update behavior ('only the supplied fields are changed'). However, it omits permissions needed, error scenarios, and overall effect on the user object. Adequate but not comprehensive.

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% (baseline 3). The description adds extra meaning: country_code/state_code must follow ISO-3166 Alpha-2, is_active requires boolean and false deactivates user. This enhances understanding beyond the schema alone.

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 title and description explicitly state 'Updates the specified project user.' The verb 'update' and resource 'project user' are clear. Although the description contains redundancy, the purpose is unmistakable and distinct among sibling update tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like create or bulk update. There are parameter-level hints (e.g., ISO-3166 format for country/state codes, is_active behavior), but no selection criteria or context for tool choice.

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