Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Custom Field

update_custom_field

Updates an existing custom field's name, description, values, and settings for a Procore company. Requires company ID and field ID.

Instructions

Updates an existing Custom Field for a given company ID. The type property cannot be modified after creation. Use this to perform the update custom action on Custom - Configurable Tools. Creates a new Custom - Configurable Tools and returns the created object on success (HTTP 201). 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
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...
field_idYesURL path parameter — uUID of the Custom Field.
nameNoJSON request body field — the updated name of the Custom Field.
can_filterNoJSON request body field — if true, allows this field to be used as a filter.
integration_onlyNoJSON request body field — if true, only integrations can update this field.
on_projectsNoJSON request body field — if true, the field is available on Projects.
on_peopleNoJSON request body field — if true, the field is available on People.
descriptionNoJSON request body field — a description to help Admin users understand the field’s purpose.
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.
Behavior3/5

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

Annotations add minimal info (all false except openWorldHint). The description reveals the HTTP method (POST), success status (201), and the constraint that 'type' cannot be modified. However, the contradictory creation statement undermines trust.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise but includes extraneous details like the full API endpoint and Procore path. The contradiction wastes space and could confuse rather than clarify.

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

Completeness2/5

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

No output schema is provided, so the description should explain the return value. It says 'returns the created object' but does not specify what that object contains. The tool has 10 parameters and complex behavior (update vs. create), so more detail is needed for complete understanding.

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?

The input schema has 100% description coverage for all 10 parameters, so the description need only add context. It mentions required parameters and the immutability of 'type', which adds marginal value beyond the schema.

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

Purpose2/5

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

The description states 'Updates an existing Custom Field' but later says 'Creates a new Custom - Configurable Tools and returns the created object on success (HTTP 201)', contradicting the primary action. This confusion reduces clarity for an agent choosing between create and 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 Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like create_custom_field or other update tools. The phrase 'Use this to perform the update custom action' provides limited context but no exclusions or comparisons.

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