Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Configurable Field Set

update_configurable_field_set
Idempotent

Update an existing configurable field set in Procore for a specified company. Send only fields to change; omitted fields keep their current values.

Instructions

Updates an existing configurable field set for the specified Procore company. Send only the fields you intend to change; omitted fields keep their current values. 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 configurable field set 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, configurable_field_set. Procore API (v2.1): Company Admin > Custom - Configurable Tools. Endpoint: PATCH /rest/v2.1/companies/{company_id}/configurable_field_sets/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — configurable Field Set ID
company_idYesURL path parameter — unique identifier for the company.
custom_field_sectionsNoJSON request body field — custom_field_sections
configurable_field_setYesJSON request body field — configurable_field_set
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds key behavioral traits: partial update behavior, company_id default, return of the modified configurable field set, and detailed error statuses (401/403/404). This significantly aids the agent in anticipating 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 front-loaded with the primary purpose and then delivers essential details. It is somewhat long but every sentence contributes value; the redundant listing of required parameters is a minor inefficiency.

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?

With no output schema, the description explains the successful return value and error payload format. It covers prerequisites, default behavior, and endpoint context. It omits detailed structure of custom_field_sections, but the schema handles that, making the description sufficient.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining partial update semantics for body fields and the default behavior for company_id, which are not inferable from the schema alone.

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 it 'Updates an existing configurable field set for the specified Procore company,' using a specific verb+resource+scope. It distinguishes from siblings like create/delete by emphasizing 'existing' and partial update semantics.

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: states that omitted fields keep current values, company_id defaults to procore_set_config, and id must be resolved with the matching list tool first. However, it does not explicitly name alternatives or state when not to use this 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