Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Company Person

create_company_person

Create a new company person in Procore by providing company_id and last_name. It returns the created person with its new id or an error payload with HTTP status.

Instructions

Create a new Company Person. Pass the record's fields as top-level arguments — they are nested under "person" in the request payload for you. company_id defaults to the value set by procore_set_config when omitted. Creates the company person and returns it with its new id (HTTP 201); calling it again creates another record. 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: company_id, last_name. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/companies/{company_id}/people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
activeNoJSON request body field — the active status of the Company Person
job_titleNoJSON request body field — the Job Title of the Company Person
last_nameYesJSON request body field — the Last Name of the Company Person
origin_idNoJSON request body field — the Origin ID of the Company User
company_idYesURL path parameter — unique identifier for the Procore company
first_nameNoJSON request body field — the First Name of the Company Person
employee_idNoJSON request body field — the Employee ID of the Company Person
is_employeeNoJSON request body field — the Employee status 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?

Beyond the annotations (readOnlyHint false, idempotentHint false), the description discloses that calling it again creates another record (non-idempotent), returns the new id with HTTP 201, and describes failure modes (401, 403, 404). This adds useful behavioral context beyond what annotations already convey.

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

Conciseness5/5

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

The description is information-dense yet tightly structured. Every sentence adds value: purpose, payload handling, default, return value, idempotency, error cases, required params, and API reference. There is no fluff or redundancy.

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?

With no output schema, the description compensates by stating the return value (new id, HTTP 201) and error payload structure. It covers defaults, required parameters, endpoint, and the non-idempotent nature. This is complete for a create tool with a well-documented schema.

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 baseline is 3. The description goes further by explaining that all record fields are nested under 'person' in the payload (semantic meaning) and that company_id defaults to the configured value. These details are not in the schema, adding real value.

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 the action ('Create a new Company Person') with a specific verb and resource, and reinforces it with the endpoint. However, it does not explicitly distinguish this from sibling tools like create_company_user, which also deal with people but create user accounts rather than directory person records.

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?

Provides clear context on how to invoke the tool: pass fields as top-level arguments, company_id defaults to procore_set_config when omitted, and required parameters are listed. It lacks an explicit 'when not to use' or comparison to alternatives, but the usage context is solid.

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