Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Vendor

update_project_vendor

Update a project vendor's details, including address, contact info, and bidding status, using specified fields.

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. Use this to update an existing Directory records (only the supplied fields are changed). Updates the specified Directory records and returns the modified object on success. 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
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Directory resource
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.
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 — the address for this Directory operation
authorized_bidderNoJSON request body field — authorized bidder status
business_phoneNoJSON request body field — the business phone for this Directory operation
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 — the mobile phone for this Directory operation
nameNoJSON 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
biddingNoJSON request body field — bidding statuses
Behavior3/5

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

Discloses partial update behavior ('only the supplied fields are changed') and return of modified object. Annotations already convey nondestructive, non-read-only nature. Additional context on permissions or side effects missing.

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?

Relatively concise, front-loaded with purpose. Includes a separate section on country codes. Could remove redundant API version/endpoint info, but overall no wasted words.

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?

Covers basic update functionality and return value. With 31 parameters and no output schema, more usage examples or typical field combinations would enhance completeness for an AI agent.

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 descriptions for each parameter. Description adds extra detail on ISO-3166 codes for country and state, but most parameters lack deeper explanation beyond schema.

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?

Description clearly states 'Update a specified Project Vendor' with verb and resource. Specifics about updating existing Directory records and returning modified object distinguish it from numerous sibling update tools.

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?

States use for updating existing records and lists required parameters. However, lacks when-not-to-use guidance or comparison with alternative tools like create or delete vendor.

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