Skip to main content
Glama
TylerIlunga

Procore MCP Server

create_project_user

Add a new user to a Procore project by specifying their contact details, permissions, and role information.

Instructions

Create project user. [Core/Directory] POST /rest/v1.0/projects/{project_id}/users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
run_configurable_validationsNoIf true, validations are run for the corresponding Configurable Field Set.
addressNoThe street Address of the Project User
avatarNoProject User Avatar. To upload avatar you must upload whole payload as `multipart/form-data` content-type and specify each parameter as form-data together with `user[avatar]` as file.
business_phoneNoThe Business Phone number of the Project User
business_phone_extensionNoThe Business Phone Extension of the Project User
cityNoThe City in which the Project User resides
country_codeNoThe Country Code of the Project User (ISO-3166 Alpha-2 format)
email_addressYesThe Email Address of the Project User
email_signatureNoThe Email Signature of the Project User
employee_idNoThe Employee ID of the Project User
fax_numberNoThe Fax Number of the Project User
first_nameNoThe First Name of the Project User
initialsNoThe Initials of the Project User
is_activeNoThe Active status of the Project User
is_employeeNoThe Employee status of the Project User
job_titleNoThe Job Title of the Project User
last_nameYesThe Last Name of the Project User
mobile_phoneNoThe Mobile Phone number of the Project User
notesNoThe Notes (notes/keywords/tags) of the Project User
permission_template_idNoThe Permission Template ID of the Project User
state_codeNoThe State Code of the Project User (ISO-3166 Alpha-2 format)
vendor_idNoThe Vendor ID of the Project User
zipNoThe Zip Code of the Project User
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It states 'Create project user' which implies a write operation, but does not mention required permissions, whether it sends notifications, if it's idempotent, or what happens on duplicate entries. The API path hints at a POST request, but lacks details on rate limits, error handling, or response format. The description is insufficient for a mutation tool with no annotation support.

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?

The description is concise with two parts: a tautological purpose and an API path. However, it is under-specified rather than efficiently informative. The API path adds technical context but does not earn its place in aiding tool selection. The structure is simple but lacks front-loaded usefulness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a 24-parameter creation tool with no annotations and no output schema, the description is inadequate. It does not explain the scope of a 'project user', required fields beyond schema, potential side effects, or what the tool returns. For a mutation tool with many parameters, more contextual information is needed to guide the agent effectively.

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?

The input schema has 100% description coverage, with detailed parameter documentation (e.g., 'Unique identifier for the project' for project_id). The description adds no parameter semantics beyond the schema, but since schema coverage is high, the baseline score of 3 is appropriate. The description does not compensate for any gaps because there are none in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create project user' is a tautology that restates the tool name without adding clarity. It does not specify what a 'project user' is or what creation entails, and it fails to distinguish this tool from sibling tools like 'create_company_user_v1_0' or 'add_company_user_to_project'. The inclusion of '[Core/Directory] POST /rest/v1.0/projects/{project_id}/users' provides API context but does not clarify the purpose.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools related to user management (e.g., 'add_company_user_to_project', 'create_company_user_v1_0'), there is no indication of prerequisites, context, or distinctions. This leaves the agent without direction on appropriate usage.

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