Skip to main content
Glama
TylerIlunga

Procore MCP Server

Updates Material Header Information.

updates_material_header_information
Idempotent

Update material header information in Procore by modifying fields such as name, description, category, and custom properties. Send only fields to change; omitted fields keep current values.

Instructions

Updates fields such as name, description, category, and custom properties on a material. The material must exist in the project scope. 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 id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified material header information 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: id, company_id, project_id. Procore API (v2.0): Resource Management > Materials Management. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/materials_mgmt/materials/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — the Id of the material
nameNoJSON request body field — name of the document header.
notesNoJSON request body field — notes associated with the document header.
stock_maxNoJSON request body field — the stock max for this Materials Management operation
stock_minNoJSON request body field — the stock min for this Materials Management operation
company_idYesURL path parameter — the company identifier
project_idYesURL path parameter — the project identifier
descriptionNoJSON request body field — description of the document header.
properties_to_addNoJSON request body field — collection of resource parameters to add to the document header.
label_guids_to_addNoJSON request body field — the label guids to add for this Materials Management operation
properties_to_deleteNoJSON request body field — collection of resource parameters to delete from the document header.
properties_to_updateNoJSON request body field — collection of resource parameters to update in the document header.
label_guids_to_removeNoJSON request body field — label_guids_to_remove
Behavior4/5

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

Beyond the annotations, the description discloses error response structures (401/403/404), returns the modified material on success, and explains PATCH semantics (only changed fields are sent). It also notes the config fallback for company/project IDs, adding useful behavioral context not present in the annotations.

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 somewhat long but well-structured and front-loaded with purpose. Every sentence contributes meaningful information: purpose, preconditions, partial-update semantics, config defaults, return value, error handling, and endpoint. There is no redundancy, but a shorter version could pack the same essentials.

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?

The description covers preconditions, usage patterns, return value, error handling, and the API endpoint, which is quite complete given the schema and annotations. It does not elaborate the format of properties_to_add/delete/update arrays beyond the schema's vague descriptions, but the 'custom properties' mention gives some clue. Since there is no output schema, the return-value description is valuable.

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?

The schema already covers all 13 parameters with descriptions (100% coverage). The description enhances understanding by explaining the default values for company_id/project_id, the need to resolve id via a list tool, and the partial-update behavior where omitted fields retain current values. This adds value beyond the schema's field-level descriptions.

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 'Updates fields such as name, description, category, and custom properties on a material,' specifying a concrete verb and resource. It distinguishes itself as a header-update operation for a single material, which is distinct from sibling tools like list_materials, create_material, and bulk_update_materials.

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?

The description provides strong usage guidance: the material must exist, partial updates are used (omitted fields keep current values), company_id/project_id default to config values, and id should be resolved via a list tool first. However, it does not explicitly name alternative tools for different scenarios (e.g., create_material or bulk_update_materials).

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