Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company Person

update_company_person

Update an existing company person's directory record in Procore by providing company ID, person ID, and last name. Modify optional fields like first name, job title, or employee ID.

Instructions

Update the specified Company Person. 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. Procore API: Core > Directory. Endpoint: PATCH /rest/v1.0/companies/{company_id}/people/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the Procore company
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). If a valid view is not provided, it will default to normal.
first_nameNoJSON request body field — the First Name of the Company Person
last_nameYesJSON request body field — the Last Name of the Company Person
is_employeeNoJSON request body field — the Employee status of the Company Person
employee_idNoJSON request body field — the Employee ID of the Company Person
activeNoJSON request body field — the active status of the Company Person
origin_idNoJSON request body field — the Origin ID of the Company User
job_titleNoJSON request body field — the Job Title of the Company Person
work_classification_idNoJSON request body field — the unique identifier for the work classification of the Company Person.
Behavior4/5

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

Annotations indicate a non-read-only, non-destructive, non-idempotent mutation. The description adds valuable context: 'only the supplied fields are changed' implying a partial update (PATCH semantics), and that the modified object is returned on success. No contradictions with annotations.

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 relatively concise (3 sentences) and front-loaded with the primary action. It efficiently conveys purpose, behavior, and required parameters without superfluous information.

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?

Given 11 parameters, no output schema, and moderate annotations, the description is adequate but not exhaustive. It covers purpose, update behavior, required params, and endpoint, but does not describe the return object structure or potential error conditions. Since there is no output schema, the description could usefully summarize the response shape.

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 description coverage is 100%, so the baseline is 3. The description adds value by explicitly calling out the required parameters (company_id, id, last_name) and noting that company_id and id are path parameters. This helps the agent prioritize necessary fields beyond what the schema provides.

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 description clearly states the tool updates a Company Person, specifies it is for existing Directory records, and mentions partial update behavior (only supplied fields changed). It also provides the Procore API endpoint, distinguishing it clearly from sibling tools like create_company_person or update_project_person.

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 instructs to use this tool for updating existing Directory records and lists required parameters. However, it does not explicitly exclude use cases or mention alternatives among the many person-related sibling tools, leaving some ambiguity about when to prefer this over other update person endpoints.

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