Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company Vendor

update_company_vendor

Update an existing vendor in the Procore company directory by providing the vendor ID, company ID, and updated vendor data. Only supplied fields are changed.

Instructions

Update a specified Company 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: id, company_id, vendor. Procore API: Core > Directory. Endpoint: PATCH /rest/v1.0/vendors/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Directory resource
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). The default view is extended.
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
company_idYesJSON request body field — unique identifier for the Procore company
vendorYesJSON request body field — the vendor for this Directory operation
Behavior4/5

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

Annotations show readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds partial update behavior ('only the supplied fields are changed') and ISO-3166 validation for country/state codes, providing useful context beyond annotations.

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 concise, front-loads the purpose, and includes necessary details (ISO codes, link, endpoint info) without unnecessary fluff. Every sentence is informative.

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?

Given the tool's complexity (5 parameters, nested vendor object, no output schema), the description covers the update behavior, required parameters, and ISO code constraints well. It could briefly mention the 'view' parameter but schema already describes it.

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% (baseline 3). The description adds specific validation rules for country_code and state_code (ISO-3166), which are not detailed in the schema descriptions, and lists required parameters, adding meaning beyond the 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?

The description clearly states 'Update a specified Company Vendor' and further clarifies that it updates existing Directory records, returning the modified object. This distinguishes it from create, delete, or list tools 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 Guidelines4/5

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

The description indicates when to use: to update existing vendors with partial field updates. It lists required parameters but does not explicitly state when not to use or name alternatives, though the context is clear for an update operation.

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