Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Cost Item

update_cost_item
Idempotent

Modify an existing cost catalog record in Procore by updating only the fields you specify. Returns the updated cost item.

Instructions

Update Cost Item. Use this to update an existing Cost Catalog records (only the supplied fields are changed). Updates the specified Cost Catalog records and returns the modified object on success. Required parameters: item_id, company_id, type, name, unit, catalog_id. Procore API (v2.0): Preconstruction > Cost Catalog. Endpoint: PUT /rest/v2.0/companies/{company_id}/estimating/catalogs/items/{item_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesURL path parameter — unique identifier of the item
company_idYesURL path parameter — unique company identifier associated with the Procore User Account.
typeYesJSON request body field — the type of the cost item.
nameYesJSON request body field — the name of the cost item.
descriptionNoJSON request body field — the description of the cost item.
unit_costNoJSON request body field — the unit cost of the cost item.
unit_laborNoJSON request body field — the unit labor required for the cost item.
unit_labor_costNoJSON request body field — the cost of the unit labor.
manufacturerNoJSON request body field — the manufacturer of the cost item.
catalog_numberNoJSON request body field — the catalog number of the cost item.
supplierNoJSON request body field — the supplier of the cost item.
cost_type_codeNoJSON request body field — the cost type code associated with the cost item. Applicable only for items categorized under a Custom cost type.
cost_type_nameNoJSON request body field — the name of the cost type associated with the cost item. Applicable only for items categorized under a Custom cost type.
wasteNoJSON request body field — the waste percentage associated with the cost item.
material_wasteNoJSON request body field — the waste percentage associated with the cost item.
item_marginNoJSON request body field — the margin applied to the cost item.
labor_marginNoJSON request body field — the margin applied to the labor for the cost item.
unit_labor_rateNoJSON request body field — the unit labor rate for the cost item.
is_untaxedNoJSON request body field — indicates whether the cost item is untaxed.
unitYesJSON request body field — the unit of measurement for the cost item. (17 possible values)
notesNoJSON request body field — any additional notes about the cost item.
colorNoJSON request body field — the color associated with the cost item.
catalog_idYesJSON request body field — the catalog ID associated with the cost item.
sub_itemsNoJSON request body field — array of sub-items associated with the cost item. Ignore unless you are creating an Assembly.
Behavior3/5

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

Annotations already indicate a non-read-only, non-destructive, idempotent mutation. The description adds that only supplied fields are changed and the modified object is returned, but lacks details on authentication, rate limits, or error handling. 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 concise (4 sentences) and front-loads the core purpose and behavior. Every sentence adds value: purpose, partial update behavior, required parameters, and API context. No fluff.

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

Completeness3/5

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

For a mutation tool with 24 parameters and no output schema, the description adequately covers basic behavior (partial update, return value) and required parameters. However, it does not explain the effect on omitted optional fields, error scenarios, or usage patterns, which would be helpful given the complexity.

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, so the schema already documents each parameter. The description only reiterates the required parameter list, adding no new semantic meaning beyond what the schema provides.

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 the verb 'Update' and the resource 'Cost Catalog records/items', distinguishing it from sibling tools like create_cost_item. It also provides the API endpoint and required parameters, making the purpose unambiguous.

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 guidance is given on when to use this tool versus alternatives (e.g., create, delete, or other update tools). The description does not mention prerequisites, conditions, or exclude scenarios, leaving the agent without decision-making context.

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