Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Person

create_project_person

Create a new reference user in a Procore project directory. Provide project ID and last name to add a person record.

Instructions

Create a new Person in the specified Project. This endpoint can currently only create reference users. It cannot create a user who can login. 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: project_id, last_name. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/projects/{project_id}/people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
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...
first_nameNoJSON request body field — the First Name of the Project Person
last_nameYesJSON request body field — the Last Name of the Project Person
is_employeeNoJSON request body field — the Employee status of the Project Person
employee_idNoJSON request body field — the Employee ID of the Project Person
origin_idNoJSON request body field — the ID of the External Data associated with the Project Person
job_titleNoJSON request body field — the Job Title of the Project Person
work_classification_idNoJSON request body field — the unique identifier for the work classification of the Project Person.
Behavior4/5

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

Annotations indicate a write operation (readOnlyHint=false). The description adds that it creates directory records and returns the created object on success, and explicitly states the limitation to reference users. This provides useful behavioral context beyond 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 concise with 4 sentences, front-loading the main action. It includes the API endpoint which may be slightly redundant but does not detract significantly.

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?

Given the exhaustive schema descriptions and annotations, the description is complete. It covers the type of user created, required parameters, success response, and API endpoint. No output schema exists, but the return value is mentioned.

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?

Schema coverage is 100% with detailed descriptions for each parameter. The description only mentions required parameters (project_id, last_name) and does not add significant meaning beyond the schema, so a baseline of 3 is appropriate.

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 Person in a specified Project, specifically reference users. It distinguishes from login-capable users. However, it does not differentiate among sibling tools like create_a_person or create_company_person, though the project scope is implied by the tool name.

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?

It mentions that it can only create reference users and not login-capable users, which guides when to use this tool. However, it does not explicitly state when to use alternatives or provide comprehensive when-to-use guidance.

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