Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Custom Field Metadatum

update_custom_field_metadatum
Idempotent

Update a Procore custom field metadatum by specifying only fields to change; omitted fields keep current values. Resolve the record ID first.

Instructions

Updates an existing custom field metadatum for the specified Procore company. 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 "custom_field_metadatum" in the request payload for you. company_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 custom field metadatum 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: company_id, id, custom_field_definition_id, host_type, source_type, source_id, position. Procore API (v2.0): Company Admin > Custom - Configurable Tools. Endpoint: PATCH /rest/v2.0/companies/{company_id}/custom_field_metadata/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — custom Field Metadatum ID
rowNoJSON request body field — row the Field is position on the Form
viewNoQuery string parameter — the extended view provides what is shown below. The default view returns the same as the extended view but excludes the attributes company_id, host_type, source_type, source_id, label, data_type, v...
columnNoJSON request body field — column the Field is position on the Form
visibleNoJSON request body field — whether or not the Custom Field Metadatum is visible
positionYesJSON request body field — the position for this Custom - Configurable Tools operation
requiredNoJSON request body field — whether or not the Custom Field Metadatum is required
host_typeYesJSON request body field — procore Entity
source_idYesJSON request body field — configurable FieldSet ID
company_idYesURL path parameter — unique identifier for the company.
source_typeYesJSON request body field — configurable FieldSet Class
column_widthNoJSON request body field — how many columns the field spans on the Form
custom_fields_section_idNoJSON request body field — custom Fields Section ID
custom_field_definition_idYesJSON request body field — custom Field Definition ID
Behavior5/5

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

Goes well beyond annotations by describing partial-update behavior, payload nesting handled for the caller, company_id defaulting, success return value, and specific HTTP error causes (401, 403, 404). This gives the agent a rich behavioral model without contradicting annotations.

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 lengthy but every sentence contributes: purpose, partial update, parameter handling, id resolution, returns, errors, and API reference. Slight redundancy in listing required parameters (already in schema) and endpoint, but overall well-front-loaded and purposeful.

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?

Covers all critical operational aspects: what the tool does, how to use it (partial update), prerequisites, default behavior, success/failure responses, and API location. Despite no output schema, the return value is mentioned and error handling is explicit, making it complete for an update operation.

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 already documents all 14 parameters with descriptions (100% coverage). The description adds valuable context: fields are passed as top-level args despite being nested in the payload, company_id has a default via procore_set_config, and required parameters are listed. This exceeds the baseline.

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 'Updates an existing custom field metadatum for the specified Procore company' – a specific verb and object. It also provides the PATCH endpoint, distinguishing it from create/show/list custom field tools in the sibling list.

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?

Provides clear usage context: partial update semantics ('Send only the fields you intend to change'), prerequisite id resolution ('resolve it with the matching list tool first'), and company_id default behavior. Does not explicitly name alternatives, but the guidance is sufficient for an update tool.

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