Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Vendor

update_project_vendor
Idempotent

Update a specified project vendor in Procore by sending only the fields you intend to change; omitted fields keep current values.

Instructions

Update a specified 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. Send only the fields you intend to change; omitted fields keep their current values. 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, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified project vendor on success. 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, id. Procore API (v1.1): Core > Directory. Endpoint: PATCH /rest/v1.1/projects/{project_id}/vendors/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Directory resource
zipNoJSON request body field — postal/ZIP code
cityNoJSON request body field — the city for this Directory operation
nameNoJSON request body field — the name for this Directory operation
viewNoQuery string parameter — the normal view provides what is shown below. The extended view is the same as the normal view but includes children_count, legal_name, parent, and bidding. The default view is normal.
notesNoJSON request body field — notes (notes/keywords/tags)
addressNoJSON request body field — the address for this Directory operation
biddingNoJSON request body field — bidding statuses
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 — the mobile phone for this Directory operation
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 — the business phone for this Directory operation
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?

The description adds substantial behavioral detail beyond the annotations: partial-update semantics (PATCH), the fact that fields are nested under 'vendor' in the payload, project_id defaulting behavior, return value on success, and specific HTTP error codes (401/403/404) with their meanings. This goes well beyond what readOnlyHint=false and idempotentHint=true convey.

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 longish but every sentence contributes: purpose, format constraints, PATCH semantics, defaulting, id resolution, return/error behavior, required params, and endpoint. It's front-loaded with the core purpose and uses structured sections (####) for readability. Not perfectly streamlined, but highly information-dense with no fluff.

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

Completeness4/5

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

For a 31-parameter mutation tool with no output schema, the description covers the essential operational context: what fields to send, how to handle project_id/id, what to expect on success and failure, and the API endpoint. It could mention the run_configurable_validations query parameter or the view parameter, but the schema already describes those, so the description remains sufficiently complete.

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?

The input schema has 100% parameter descriptions, so the baseline is 3. The description adds useful clarifications beyond the schema: country/state code format (though schema already mentions ISO-3166 Alpha-2), top-level argument vs. nested 'vendor' payload handling, and project_id defaulting to procore_set_config even though schema marks it required. These details help an agent avoid common mistakes.

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 'Update a specified Project Vendor' — a specific verb and resource — and is clearly differentiated from sibling tools like create_project_vendor, list_project_vendors, and show_project_vendor. The endpoint line (PATCH /rest/v1.1/projects/{project_id}/vendors/{id}) reinforces the update operation.

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?

It gives actionable context: 'Send only the fields you intend to change; omitted fields keep their current values' and explicitly advises 'resolve it with the matching list tool first' for the id parameter. It also notes the project_id default from procore_set_config. It doesn't explicitly state when NOT to use it for create/list, but the update purpose plus the id-resolution instruction provide clear usage direction.

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