Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Asset

update_asset_company
Idempotent

Update a company asset's details in Procore by sending only the fields you want to change; omitted fields retain their current values. Returns the modified asset.

Instructions

Updates the company asset model based on keys in the request body. 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 asset_id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified asset 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: asset_id, company_id. Procore API (v2.0): Core > Assets. Endpoint: PATCH /rest/v2.0/companies/{company_id}/assets/{asset_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoJSON request body field — notes by context. Keys are context identifiers; value is the note text. Supported keys: "asset_status" (stored only when status is changed in this request), "project_assignment" (stored when provid...
asset_idYesURL path parameter — unique identifier for the asset
latitudeNoJSON request body field — latitude must be provided together with longitude, or both must be omitted. Pass null to clear.
trade_idNoJSON request body field — trade ID. Pass null to clear the value.
longitudeNoJSON request body field — longitude must be provided together with latitude, or both must be omitted. Pass null to clear.
asset_codeNoJSON request body field — unique identifier for the asset (also referred to as asset_code in API)
asset_nameNoJSON request body field — name of the asset
company_idYesURL path parameter — unique identifier for the company.
descriptionNoJSON request body field — description of the asset. Pass null to clear the value.
location_idNoJSON request body field — location ID. Pass null to clear the value.
asset_type_idNoJSON request body field — asset type ID. Must have Is Asset enabled for that type. If asset type is changed, all custom fields will be reset and only the ones provided in this request will be set.
custom_fieldsNoJSON request body field — custom fields map with merge semantics. Key: 'custom\_field\_{id}'. Only fields included in this map will be updated - absent fields remain unchanged. To remove a specific field, set its value to n...
Accept-LanguageNoJSON request body field — locale for localized response messages (for example: en, fr-FR, pseudo)
asset_status_idNoJSON request body field — unique identifier of the asset status
parent_asset_idNoJSON request body field — parent asset ID. Pass null to remove parent (make standalone). The parent must exist, belong to the same company, and be in the same asset type hierarchy.
profile_image_idNoJSON request body field — profile image FAS ID. Pass null to clear the value.
cascade_ancestorsNoJSON request body field — when the new parent (or any of its ancestors) is at company scope or on a different project than the child, opt in to cascade-pull those ancestors into the child's project. Defaults to false (retur...
wrap_custom_fieldsNoQuery string parameter — when true, wraps each custom field value as {"value": ...} and renames "name" to "label" inside LOV objects.
acknowledge_warningsNoQuery string parameter — when true, acknowledges field-default warnings and applies default values for read-only fields whose current value differs from the configured default.
Behavior5/5

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

Annotations only provide readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds PATCH-style partial update semantics, company_id defaulting to the procore_set_config value, the requirement that asset_id resolve to an existing record, the success return value, and concrete HTTP error scenarios (401, 403, 404) — all valuable beyond annotations with no contradiction.

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: purpose, patch behavior, prerequisites, return/error behavior, required parameters, and endpoint are each covered in a sentence or clause. No filler or repetition of schema details, and it's front-loaded with the core verb and scope.

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?

With no output schema, the description still discloses the success return value and error payload structure, and per-parameter meaning is fully supplied by the schema. The endpoint and required parameters are explicit, making the tool adequately specified for an agent to select and invoke.

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 coverage is 100%, so the baseline is 3. The description adds the crucial merge/patch semantics across all body fields ('Send only the fields you intend to change; omitted fields keep their current values') and clarifies that company_id can be omitted thanks to a config default, which is not obvious 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 opens with 'Updates the company asset model based on keys in the request body' — a specific verb and resource that clearly defines what the tool does. This distinguishes it from sibling tools like create/delete/list assets and the project-scoped update_asset_project.

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 states to send only changed fields and that omitted fields keep their values, and instructs to resolve asset_id with the matching list tool first because it must identify an existing parent record. It does not explicitly name alternative tools or exclusion conditions, so clear context is present but explicit when-not-to-use guidance is missing.

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