Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Checklist Item (Deprecated)

update_checklist_item
Idempotent

Update a checklist item in Procore by supplying list, item, project, and section IDs plus the item fields to change. Omitted fields retain their current values.

Instructions

Updates Checklist Item in a specified Checklist. DEPRECATED: Procore has deprecated this endpoint (as of 2022-01-27). It may be removed without further notice; prefer a newer version of this resource where one exists, and use procore_search_endpoints to find it. Send only the fields you intend to change; omitted fields keep their current values. list_id, id must identify existing parent records — resolve them with the matching list tool first. Returns the modified checklist item 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: list_id, id, project_id, section_id, item. Procore API: Project Management > Inspections. Endpoint: PATCH /rest/v1.0/checklist/lists/{list_id}/items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Inspections resource
itemYesJSON request body field — item object
list_idYesURL path parameter — unique identifier of the list
project_idYesJSON request body field — the ID of the Project the Item belongs to
section_idYesJSON request body field — the ID of the Section the Item belongs to
attachmentsNoJSON request body field — item's Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files.
Behavior5/5

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

Beyond annotations, the description discloses PATCH partial-update semantics ("Send only the fields you intend to change; omitted fields keep their current values"), return value ("Returns the modified checklist item on success"), error status meanings (401/403/404), and deprecation risk. This significantly enriches the agent's understanding of tool behavior.

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 dense yet every sentence earns its place: purpose, deprecation, partial update, prerequisites, return/errors, required params, and endpoint. It is front-loaded with the most important information and contains no fluff.

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

Completeness5/5

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

With no output schema, the description covers the return value and error behavior. It also includes required parameters, identity resolution steps, deprecation status, API category, and HTTP endpoint. This is a complete picture for an agent to make an informed selection and invocation.

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?

Even though schema coverage is 100%, the description adds valuable context by explaining partial update behavior, mandatory parameters, and the requirement to resolve list_id/id with the matching list tool. It does not elaborate on the `item` object structure or `attachments`, which would push it to a 5.

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 opens with a clear verb+resource statement: "Updates Checklist Item in a specified Checklist." It distinguishes this tool from sibling tools like update_checklist by focusing on the checklist item resource, and the deprecation notice adds essential context without obscuring the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says the endpoint is deprecated and directs the agent to "prefer a newer version of this resource where one exists, and use procore_search_endpoints to find it." It also advises resolving list_id and id with the matching list tool first, providing clear when-to-use and 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