Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Company Person

create_company_person

Create a new company person in Procore's directory. Required: company ID and last name. Optional: first name, job title, employee ID, work classification, and active status.

Instructions

Create a new Company Person. Use this to create a new Directory records in Procore. Creates a new Directory records and returns the created object on success (HTTP 201). Required parameters: company_id, last_name. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/companies/{company_id}/people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the Procore company
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?

Adds useful operational details such as the API section (Core > Directory), endpoint, and HTTP 201 response. Annotations already indicate write operation; description provides extra context without contradictions.

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?

Contains redundancy (e.g., 'Create a new Company Person' and 'Creates a new Directory records' are repetitive). Key information is present but could be more streamlined.

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?

Lacks description of the returned object structure (no output schema), does not explain the 'view' parameter or other optional fields. Given the complexity (10 params), the description is somewhat incomplete.

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?

Input schema has 100% description coverage, so baseline is 3. Description only restates required parameters (company_id, last_name) without adding meaning 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 it creates a new Company Person / Directory record in Procore, but does not differentiate from similar tools like create_company_user or create_project_person, which could cause an AI agent to be unsure which tool to use.

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

Usage Guidelines3/5

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

The description mentions required parameters but provides no guidance on when to use this tool versus alternatives, nor does it state prerequisites or when not to use it.

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