Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Field Rule (Project Scope)

update_field_rule_project_scope
Idempotent

Update a project-scoped field rule's name, description, active status, definition, or fieldset. Scope fields (asset type, trigger field, rule type) are immutable; send only fields to change.

Instructions

Updates a project-scoped field rule's definition / metadata. The rule must belong to the given project. Scope fields (assetTypeId, triggerField, ruleType) cannot be changed. Send only the fields you intend to change; omitted fields keep their current values. company_id and project_id default to the values set by procore_set_config when omitted, and rule_id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified field rule 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, project_id, rule_id. Procore API (v2.0): Core > Assets. Endpoint: PUT /rest/v2.0/companies/{company_id}/projects/{project_id}/assets/settings/field_rules/{rule_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rule_idYesURL path parameter — unique identifier for the field rule.
is_activeNoJSON request body field — whether the rule is active. Set to false to deactivate.
rule_nameNoJSON request body field — display name for the rule
rule_typeNoJSON request body field — optional metadata. NOT updatable: if provided, must match the existing rule's type; the server rejects mismatches.
company_idYesURL path parameter — unique identifier for the company.
definitionNoJSON request body field — rule definition. Shape must match the rule's stored type — for NAMING, supply expression_fields; for FIELD_DEFAULTS, supply actions. Sent as a raw JSON object; the server converts it to the correct...
project_idYesURL path parameter — unique identifier for the project.
descriptionNoJSON request body field — optional description
fieldset_idNoJSON request body field — new fieldset id. FIELD_DEFAULTS only; ignored / rejected for NAMING. Provided to recover a rule whose asset type's fieldset has been changed by an admin. Must match the asset type's current fieldse...
Accept-LanguageNoJSON request body field — locale for localized response messages (for example: en, fr-FR, pseudo)
Behavior5/5

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

Beyond annotations (non-read-only, idempotent, non-destructive), the description adds valuable context: partial updates, immutability of scope fields, defaulting of company_id/project_id from procore_set_config, and detailed error statuses (401/403/404). No contradiction with 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 compact yet information-dense, structured logically: purpose, constraints, update semantics, config defaults, return value, error handling, required parameters, and endpoint reference. No wasted sentences.

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?

For a tool with 10 parameters, a nested definition object, and many siblings, the description covers the essential operational aspects: what is updated, what cannot change, how IDs are resolved and defaulted, what a successful response looks like, and how failures manifest. The endpoint and API section add completeness.

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 descriptions already cover parameters, but the description adds operational meaning: company_id/project_id default from procore_set_config when omitted, and rule_id must exist and be resolved via a list tool. It also clarifies the partial-update behavior across body parameters, which the schema alone does not convey.

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 a project-scoped field rule's definition/metadata, which is specific and distinguishes it from company-scoped or create/delete tools. It immediately mentions constraints like non-changeable scope fields, making the tool's purpose unmistakable.

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?

It advises resolving rule_id with the matching list tool first and explains partial-update behavior (omitted fields keep current values). It does not explicitly name alternative tools for changing scope fields or bulk updates, but the prerequisite and scope constraints give practical guidance for when this tool is appropriate.

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