Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Cost Item

create_cost_item

Create a new cost item record in Procore's Cost Catalog. Specify company, type, name, unit, and catalog ID to add items like parts, labor, or equipment.

Instructions

Create Cost Item. Use this to create a new Cost Catalog records in Procore. Creates a new Cost Catalog records and returns the created object on success (HTTP 201). Required parameters: company_id, type, name, unit, catalog_id. Procore API (v2.0): Preconstruction > Cost Catalog. Endpoint: POST /rest/v2.0/companies/{company_id}/estimating/catalogs/items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
Behavior2/5

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

Beyond annotations, the description adds the HTTP 201 success response but does not disclose side effects, authentication requirements, rate limits, or behaviors like field validation or default values. With openWorldHint true, more behavioral context would be helpful.

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 reasonably concise, front-loading purpose and required parameters. It could be slightly more efficient by removing the redundant first sentence, but overall it is well-structured.

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?

With 23 parameters and no output schema, the description does not fully cover parameter usage (e.g., sub_items only for Assembly type). It provides basic return info but lacks examples or guidance on conditional optional fields.

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?

Schema coverage is 100%, so the description does not add significant new meaning to parameters. It repeats required parameter names, but the schema already fully describes each parameter. Baseline score of 3 is appropriate.

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 tool creates Cost Catalog records in Procore, specifies the HTTP verb (POST), success response (HTTP 201), and includes the API endpoint and required parameters. It differentiates from sibling tools by naming the specific resource (Cost Catalog items) and providing a unique endpoint.

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?

The description lacks guidance on when to use this tool versus alternatives like create_cost_code or create_catalog. It does not mention exclusions, prerequisites, or scenarios where another tool would be more 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