Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Person

update_a_person

Update a person's details in Resource Planning using company and person IDs. Modify attributes like name, status, contact info, and more.

Instructions

Updates a Person for a given company and person ID. Use this to perform the update a action on Resource Planning records. Creates a new Resource Planning records and returns the created object on success (HTTP 201). Required parameters: company_id, person_id. Procore API: Resource Management > Resource Planning. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/people/{person_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string...
person_idYesURL path parameter — unique identifier for the person
first_nameNoJSON request body field — first Name of the Person.
last_nameNoJSON request body field — last Name of the Person.
is_assignableNoJSON request body field — determines if the Person can be assigned to tasks.
statusNoJSON request body field — the status of the Person. `active` means the person is visible in all pages, while `inactive` hides the person unless filtered. Inactive People do not count against billing plans.
group_idsNoJSON request body field — array of UUIDs representing the Groups this Person belongs to. **Cannot be empty** for an assignable resource or a non-admin Person.
emailNoJSON request body field — the email that the Person will log in with. **Required if updating `is_user` to `true`**. Must be unique across the company.
permission_level_idNoJSON request body field — uUID of the Permission Level assigned to the Person. **Required when setting `is_user: true`**.
notification_profile_idNoJSON request body field — uUID of the Notification Profile for the user.
phoneNoJSON request body field — the Person's phone number, including country and area code. Must be **unique** among all registered People.
can_receive_smsNoJSON request body field — determines if the Person can receive SMS notifications.
can_receive_emailNoJSON request body field — determines if the Person can receive email notifications.
can_receive_mobileNoJSON request body field — determines if the Person can receive mobile push notifications if they have the app installed.
address_1NoJSON request body field — first part of the Person's address.
address_2NoJSON request body field — second part of the Person's address (e.g., Apartment, Suite, Unit).
city_townNoJSON request body field — the city or town where the Person is located.
state_provinceNoJSON request body field — the state or province where the Person is located.
zipcodeNoJSON request body field — the postal/zip code of the Person.
countryNoJSON request body field — the country where the Person is located.
job_title_idNoJSON request body field — uUID reference to a Job Title in the LaborChart System.
hourly_wageNoJSON request body field — hourly wage rate for the Person. Used for automatic spend tracking.
employee_numberNoJSON request body field — internal employee identifier.
emergency_contact_nameNoJSON request body field — name of the Person's emergency contact.
emergency_contact_numberNoJSON request body field — phone number of the emergency contact.
emergency_contact_emailNoJSON request body field — email address of the emergency contact.
emergency_contact_relationNoJSON request body field — the relationship between the Person and their emergency contact.
dobNoJSON request body field — date of birth of the Person. Accepts ISO Date String, UTC Date String, or MS Numeric Epoch Time.
hired_dateNoJSON request body field — date the Person was hired. Accepts ISO Date String, UTC Date String, or MS Numeric Epoch Time.
is_maleNoJSON request body field — specifies if the Person identifies as male.
languageNoJSON request body field — language preference. Currently only `english` is supported.
Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the tool is a safe mutation. However, the description claims 'Creates a new Resource Planning records' and returns HTTP 201, which is typically for creation, not update. This inconsistency misleads about the actual behavior (update vs. create). No details on authorization requirements, side effects, or response structure are provided beyond the HTTP status.

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

Conciseness3/5

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

The description is moderately concise but includes redundant information (Procore API line, endpoint URL) and a confusing creation statement. It could be shorter without losing clarity. The structure is adequate but not streamlined.

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

Completeness2/5

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

Given the tool has 31 parameters, no output schema, and a potentially non-obvious behavior (update vs. create), the description should provide more context. It lacks explanation of what happens to existing data, required permissions, or how the tool differs from similar ones. The contradiction between 'Update' and 'Creates new records' undermines completeness.

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?

The input schema has 31 parameters with 100% description coverage. The description only repeats that company_id and person_id are required, adding no new meaning. Since schema coverage is high, baseline 3 is appropriate; the description offers marginal extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Updates a Person for a given company and person ID,' which clearly identifies the resource and action. However, it also says 'Creates a new Resource Planning records,' which contradicts the update intention and introduces ambiguity. The purpose is partially clear but needs resolution of the creation reference.

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?

The description tells users to use this tool for 'the update a action on Resource Planning records,' providing some context. But it offers no when-to-use or when-not-to-use guidance compared to sibling update tools (e.g., update_company_person, update_project_person) or create tools. No alternatives or exclusions are mentioned.

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