Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Generic Tool Item

update_generic_tool_item

Update attributes of a Generic Tool Item in Procore, such as description, due date, status, or custom fields. Only supplied fields are changed.

Instructions

Update a Generic Tool Item's attributes. For more information on Generic Tool and Correspondence Tool endpoints, see Working with the Correspondence Tool. Use this to update an existing Custom - Configurable Tools (only the supplied fields are changed). Updates the specified Custom - Configurable Tools and returns the modified object on success. Required parameters: generic_tool_item_id, generic_tool_id, project_id. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: 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_idYesURL path parameter — unique identifier for the Generic Tool Item
generic_tool_idYesURL path parameter — unique identifier for the Generic Tool
project_idYesURL path parameter — unique identifier for the project.
viewNoQuery string parameter — if supplied customize the response format
descriptionNoJSON request body field — the description of the generic tool item.
due_dateNoJSON request body field — the due date for the generic tool item.
positionNoJSON request body field — the position/number of the generic tool item.
privateNoJSON request body field — if 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_emailsNoJSON request body field — if true creating and updating the item will not send emails to the users on the item.
schedule_impactNoJSON request body field — the schedule impact status for the generic tool item.
schedule_impact_valueNoJSON request body field — specifies a value for the schedue impact of the generic tool item.
cost_impactNoJSON request body field — the cost impact of the generic tool item.
cost_impact_valueNoJSON request body field — specifies a value for the cost impact of the generic tool item.
statusNoJSON request body field — the status of the generic tool item.
titleNoJSON request body field — the title of the generic tool item.
received_from_idNoJSON request body field — the unique identifier for the Received From entity.
location_idNoJSON request body field — the location identifier for the generic tool item.
cost_code_idNoJSON request body field — the cost code identifier for the generic tool item.
specification_section_idNoJSON request body field — the specification section identifier for the generic tool item.
trade_idNoJSON request body field — the trade identifier for the generic tool item.
distribution_member_idsNoJSON request body field — an array of distribution member identifiers for the generic tool item.
assignee_idsNoJSON request body field — an array of assignee identifiers for the generic tool item.
attachmentsNoJSON request body field — specifies 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}NoJSON request body field — value 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_idsNoJSON request body field — drawing Revisions to attach to the response
file_version_idsNoJSON request body field — file Versions to attach to the response
form_idsNoJSON request body field — forms to attach to the response
image_idsNoJSON request body field — images to attach to the response
upload_idsNoJSON request body field — uploads to attach to the response
document_management_document_revision_idsNoJSON request body field — pDM document to attach to the response
Behavior3/5

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

Annotations already indicate not readonly and not destructive. The description adds that updates are partial (only supplied fields changed) and returns the modified object, which provides some behavioral context beyond annotations.

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 somewhat verbose, including redundant information like the full endpoint path and category. It front-loads the purpose but could be more concise.

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?

Given the high parameter count and no output schema, the description covers purpose, partial update, and required parameters. However, it lacks details on error handling, permissions, or return value structure, leaving gaps for an agent.

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 baseline is 3. The description lists required parameters but does not add meaning beyond the schema's parameter descriptions. It provides endpoint path context but not deeper semantics.

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

Purpose4/5

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

The description clearly states it updates a Generic Tool Item's attributes and only changes supplied fields. It distinguishes itself by specifying partial update and return of modified object, but does not explicitly differentiate from siblings like batch_update_generic_tool_items.

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 (e.g., batch_update or create). It mentions 'only the supplied fields are changed' but does not provide when-not or prerequisites.

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