Skip to main content
Glama
TylerIlunga

Procore MCP Server

update_generic_tool_item

Modify generic tool items in Procore projects to update details like status, schedule impact, cost impact, assignments, attachments, and custom fields.

Instructions

Update Generic Tool Item. [Company Admin/Custom - Configurable Tools] PATCH /rest/v1.0/projects/{project_id}/generic_tools/{generic_tool_id}/generic_tool_items/{generic_tool_item_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
generic_tool_item_idYesUnique identifier for the Generic Tool Item
generic_tool_idYesUnique identifier for the Generic Tool
project_idYesUnique identifier for the project.
viewNoIf supplied customize the response format
descriptionNoThe description of the generic tool item.
due_dateNoThe due date for the generic tool item.
positionNoThe position/number of the generic tool item.
privateNoIf this property is set to true, the generic tool item is private. If this property is set to false, the generic tool item is not private.
skip_emailsNoIf true creating and updating the item will not send emails to the users on the item.
schedule_impactNoThe schedule impact status for the generic tool item.
schedule_impact_valueNoSpecifies a value for the schedue impact of the generic tool item.
cost_impactNoThe cost impact of the generic tool item.
cost_impact_valueNoSpecifies a value for the cost impact of the generic tool item.
statusNoThe status of the generic tool item.
titleNoThe title of the generic tool item.
received_from_idNoThe unique identifier for the Received From entity.
location_idNoThe location identifier for the generic tool item.
cost_code_idNoThe cost code identifier for the generic tool item.
specification_section_idNoThe specification section identifier for the generic tool item.
trade_idNoThe trade identifier for the generic tool item.
distribution_member_idsNoAn array of distribution member identifiers for the generic tool item.
assignee_idsNoAn array of assignee identifiers for the generic tool item.
attachmentsNoSpecifies an array of generic tool item attachments. To upload attachments you must upload the entire payload as a `multipart/form-data` content-type and specify each parameter as form-data togethe...
custom_field_%{custom_field_definition_id}NoValue of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
drawing_revision_idsNoDrawing Revisions to attach to the response
file_version_idsNoFile Versions to attach to the response
form_idsNoForms to attach to the response
image_idsNoImages to attach to the response
upload_idsNoUploads to attach to the response
document_management_document_revision_idsNoPDM document to attach to the response
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Update' (implying mutation) and includes a role hint, but does not disclose critical behavioral traits like required permissions, whether updates are destructive, rate limits, or response format. The PATCH method hint is minimal and not elaborated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but under-specified, not concise in a helpful way. It includes an API endpoint and role hint, but these are not front-loaded with actionable context. The single sentence lacks structure and wastes space on redundant information.

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

Completeness2/5

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

Given the complexity (30 parameters, mutation tool, no annotations, no output schema), the description is inadequate. It fails to explain the resource being updated, expected outcomes, error conditions, or integration with sibling tools. The role hint is insufficient for such a high-parameter tool.

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 description coverage is 100%, so the schema fully documents all 30 parameters. The description adds no parameter-specific information beyond what the schema provides, such as examples or constraints. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update Generic Tool Item' is a tautology that restates the tool name without adding clarity. It includes an API endpoint path and a bracketed role hint '[Company Admin/Custom - Configurable Tools]', but does not specify what a 'Generic Tool Item' is or what fields can be updated, leaving the purpose vague.

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 provided on when to use this tool versus alternatives. The bracketed role hint implies it's for company admins or custom configurable tools, but there is no explicit mention of prerequisites, when-not-to-use scenarios, or sibling tool distinctions (e.g., batch_update_generic_tool_items).

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