Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Vendor

create_project_vendor

Add a new vendor to a Procore project directory by specifying project ID and vendor name. Optionally include address, contact details, and compliance fields.

Instructions

Create a new Project Vendor. #### Country and State codes The country_code and state_code parameter values must conform to the ISO-3166 Alpha-2 specification. See Working with Country Codes for additional information. 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, name. Procore API (v1.1): Core > Directory. Endpoint: POST /rest/v1.1/projects/{project_id}/vendors

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). The default view is normal.
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
abbreviated_nameNoJSON request body field — the abbreviated name for this Directory operation
addressNoJSON request body field — street address
authorized_bidderNoJSON request body field — authorized bidder status
business_phoneNoJSON request body field — business phone number
cityNoJSON request body field — the city for this Directory operation
country_codeNoJSON request body field — country code (ISO-3166 Alpha-2 format)
email_addressNoJSON request body field — the email address for this Directory operation
fax_numberNoJSON request body field — the fax number for this Directory operation
is_activeNoJSON request body field — active status
labor_unionNoJSON request body field — the labor union for this Directory operation
license_numberNoJSON request body field — the license number for this Directory operation
mobile_phoneNoJSON request body field — mobile phone number
nameYesJSON request body field — the name for this Directory operation
non_union_prevailing_wageNoJSON request body field — non union prevailing wage status
notesNoJSON request body field — notes (notes/keywords/tags)
origin_idNoJSON request body field — unique identifier of the origin
origin_dataNoJSON request body field — the origin data for this Directory operation
origin_codeNoJSON request body field — the origin code for this Directory operation
parent_idNoJSON request body field — parent Vendor ID. Cannot be the same as ID. Only two levels of hierarchy are supported (parent/child).
prequalifiedNoJSON request body field — prequalified status
primary_contact_idNoJSON request body field — unique identifier of the primary contact
state_codeNoJSON request body field — state code (ISO-3166 Alpha-2 format)
trade_nameNoJSON request body field — vendor's Trade Name, also known as Doing Business As (DBA).
union_memberNoJSON request body field — union member status
websiteNoJSON request body field — website url
zipNoJSON request body field — postal/ZIP code
Behavior3/5

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

Annotations already indicate it's a write operation (readOnlyHint=false). The description adds that it returns the created object with HTTP 201 and notes formatting constraints on country/state codes. However, it does not disclose potential side effects like workflow triggers or duplicate handling.

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 short and front-loads the main action. However, it repeats 'Create a new Directory records' twice, which could be consolidated without loss.

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 the complexity (29 parameters) and rich schema, the description sufficiently covers purpose, required parameters, and endpoint. It lacks explanation of the view parameter, return value structure, and how this tool fits into the broader directory context.

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?

With 100% schema coverage, the baseline is 3. The description adds value by specifying ISO-3166 Alpha-2 format for country_code and state_code, which is not in the schema descriptions. It also reiterates required parameters, but that is redundant.

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 title and description clearly state the tool creates a new Project Vendor, and the endpoint path (project-level) distinguishes it from company-level vendor creation. However, it does not explain what a Project Vendor is versus a Company Vendor, which could cause confusion among siblings.

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

Usage Guidelines2/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 like create_company_vendor or bulk_create_project_vendor. It does not mention context or exclusions, leaving the agent without decision criteria.

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