Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Person

update_project_person
Idempotent

Update a project user's details with partial field updates. Returns the modified person record, with error payloads for authentication, permission, or not found issues.

Instructions

Update the specified Project User. 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 "person" in the request payload for you. project_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 project person 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: project_id, id, last_name. Procore API: Core > Directory. Endpoint: PATCH /rest/v1.0/projects/{project_id}/people/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Directory resource
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). Users without read permissions to Directory are limited to the normal and extended views. If a v...
job_titleNoJSON request body field — the Job Title of the Project Person
last_nameYesJSON request body field — the Last Name of the Project Person
origin_idNoJSON request body field — the ID of the External Data associated with the Project Person
first_nameNoJSON request body field — the First Name of the Project Person
project_idYesURL path parameter — unique identifier for the Procore project
employee_idNoJSON request body field — the Employee ID of the Project Person
is_employeeNoJSON request body field — the Employee status of the Project Person
work_classification_idNoJSON request body field — the unique identifier for the work classification of the Project Person.
Behavior5/5

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

This description goes well beyond the annotations. It discloses partial-update semantics, automatic nesting of fields under 'person', defaulting behavior for project_id, success return value, and specific HTTP error scenarios (401, 403, 404). This is rich behavioral context that helps the agent anticipate outcomes.

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 primary action and includes no filler. Each sentence contributes useful details (partial update, payload mapping, defaults, resolution steps, error codes, endpoint). It is slightly long but every part earns its place, so it remains effective.

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?

For a mutation tool without an output schema, this description is exceptionally complete. It covers the operation, parameter behavior, defaults, error responses, required parameters, API category, and endpoint. The agent has enough information to invoke the tool correctly and interpret failures.

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?

The input schema already provides 100% description coverage for all 10 parameters, giving the baseline of 3. The description adds valuable meaning by explaining that only changed fields are sent, that top-level arguments are mapped into a nested 'person' object, and that project_id can default from config. This enhances understanding beyond the schema.

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 'Update the specified Project User' with a specific verb and resource. It also clarifies the partial-update behavior and return value. However, it does not explicitly distinguish this tool from the sibling 'update_project_user', which could cause confusion in tool selection.

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?

The description provides concrete usage guidance: it says to send only changed fields, explains that project_id defaults to procore_set_config when omitted, and instructs to resolve the id with the matching list tool first. It does not, however, state when to prefer this tool over the similar 'update_project_user' or mention exclusions.

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