Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Vendor

create_project_vendor

Create a vendor record in a Procore project by providing project ID and vendor name; returns the new vendor's unique ID.

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. Pass the record's fields as top-level arguments — they are nested under "vendor" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted. Creates the project vendor 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: project_id, name. Procore API (v1.1): Core > Directory. Endpoint: POST /rest/v1.1/projects/{project_id}/vendors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoJSON request body field — postal/ZIP code
cityNoJSON request body field — the city for this Directory operation
nameYesJSON request body field — the name for this Directory operation
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). The default view is normal.
notesNoJSON request body field — notes (notes/keywords/tags)
addressNoJSON request body field — street address
websiteNoJSON request body field — website url
is_activeNoJSON request body field — active status
origin_idNoJSON request body field — unique identifier of the origin
parent_idNoJSON request body field — parent Vendor ID. Cannot be the same as ID. Only two levels of hierarchy are supported (parent/child).
fax_numberNoJSON request body field — the fax number for this Directory operation
project_idYesURL path parameter — unique identifier for the project.
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).
labor_unionNoJSON request body field — the labor union for this Directory operation
origin_codeNoJSON request body field — the origin code for this Directory operation
origin_dataNoJSON request body field — the origin data for this Directory operation
country_codeNoJSON request body field — country code (ISO-3166 Alpha-2 format)
mobile_phoneNoJSON request body field — mobile phone number
prequalifiedNoJSON request body field — prequalified status
union_memberNoJSON request body field — union member status
email_addressNoJSON request body field — the email address for this Directory operation
business_phoneNoJSON request body field — business phone number
license_numberNoJSON request body field — the license number for this Directory operation
abbreviated_nameNoJSON request body field — the abbreviated name for this Directory operation
authorized_bidderNoJSON request body field — authorized bidder status
primary_contact_idNoJSON request body field — unique identifier of the primary contact
non_union_prevailing_wageNoJSON request body field — non union prevailing wage status
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description explicitly states non-idempotency ('calling it again creates another record'), explains error payloads with common HTTP statuses (401/403/404), and documents the project_id default. This gives the agent critical operational context without contradicting structured metadata.

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 efficiently structured with a bolded section for country/state codes, and every sentence carries useful information: purpose, defaults, idempotency, error behavior, required parameters, API reference. It is moderately long but earns its length for a 29-parameter tool.

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 high complexity (29 params), full schema coverage, and no output schema, the description is remarkably complete. It covers required params, default behavior, error handling, endpoint info, and return value (new id with HTTP 201). The agent has all essential information to invoke the tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds meaning by specifying ISO-3166 Alpha-2 conformance for country_code/state_code, reassuring that fields should be passed as top-level arguments despite being nested under 'vendor' in the payload, and noting the project_id default. These details go beyond the raw schema descriptions.

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

Purpose5/5

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

The description opens with a specific verb+resource: 'Create a new Project Vendor.' It further clarifies the scope via endpoint POST /rest/v1.1/projects/{project_id}/vendors and distinguishes itself from company-level vendor creation. This is unambiguous and differentiates from siblings like list_project_vendors or update_project_vendor.

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?

The description provides clear context: it creates a project-scoped vendor, lists required parameters (project_id, name), explains project_id defaults to procore_set_config, and warns that calling again creates another record. However, it does not explicitly mention when NOT to use this tool or name alternatives (e.g., create_company_vendor for company-level vendors).

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