Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Custom Field

update_custom_field

Update an existing custom field in Procore by specifying company and field IDs. Change name, description, values, and visibility settings while keeping the field type immutable.

Instructions

Updates an existing Custom Field for a given company ID. The type property cannot be modified after creation. company_id defaults to the value set by procore_set_config when omitted, and field_id must identify an existing parent record — resolve it with the matching list tool first. Applies the change and returns the updated custom field. 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: company_id, field_id. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/custom-fields/{field_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoJSON request body field — the updated name of the Custom Field.
valuesNoJSON request body field — only applicable for `select` or `multi-select` fields. Replaces the entire list of values.
sort_byNoJSON request body field — controls sorting of dropdown values. `alpha` sorts alphabetically, while `listed` maintains the provided order.
field_idYesURL path parameter — uUID of the Custom Field.
on_peopleNoJSON request body field — if true, the field is available on People.
can_filterNoJSON request body field — if true, allows this field to be used as a filter.
company_idYesURL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string...
descriptionNoJSON request body field — a description to help Admin users understand the field’s purpose.
on_projectsNoJSON request body field — if true, the field is available on Projects.
integration_onlyNoJSON request body field — if true, only integrations can update this field.
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses several important behaviors: the type property is immutable after creation, company_id has a default configuration value, errors return HTTP status codes (401/403/404), and the tool returns the updated custom field. This rich context significantly helps the agent anticipate outcomes.

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 a single paragraph of about five sentences covering purpose, constraints, defaults, error handling, and endpoint. Every sentence is informative, though the endpoint and explicit 'Required parameters' line are slightly redundant with schema info, making it a bit denser than strictly necessary.

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?

Considering the 10-parameter schema and no output schema, the description adequately covers the tool's effect, prerequisites (resolve field_id), return value (updated custom field), and common error conditions. It is complete enough for an agent to invoke the tool correctly without further lookups.

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 coverage, providing detailed descriptions for all 10 parameters. The description adds extra meaning for the two required parameters: company_id's default behavior and field_id's need to be resolved via a list tool. It does not elaborate on the other 8 parameters, but they are already well-documented in the schema.

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 description clearly states the tool updates an existing Custom Field for a given company ID, using a specific verb and resource. It distinguishes from create/delete by emphasizing 'existing', but does not explicitly name alternatives like update_custom_field_definition, so it lacks explicit sibling differentiation.

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 helpful usage context: it instructs to resolve field_id with the matching list tool first and notes company_id defaults from procore_set_config when omitted. However, it does not explicitly state when not to use this tool or name any alternative tools, so it stops short of full when/when-not guidance.

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