Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Checklist

update_checklist

Update an existing inspection checklist in a project by changing only the supplied fields. Returns the updated checklist object.

Instructions

Updates Inspection Checklist in a specified Project. Use this to update an existing Inspections (only the supplied fields are changed). Updates the specified Inspections and returns the modified object on success. Required parameters: id, project_id, list. Procore API: Project Management > Inspections. Endpoint: PATCH /rest/v1.0/checklist/lists/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Inspections resource
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
project_idYesJSON request body field — the ID of the Project
listYesJSON request body field — checklist object
attachmentsNoJSON request body field — checklist'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.
Behavior3/5

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

Annotations already indicate non-read-only and non-destructive. The description adds that only supplied fields are changed and it returns the modified object, which are useful behavioral traits. However, it does not elaborate on side effects, permissions, or rate limits beyond what annotations imply.

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 four sentences, front-loaded with purpose, then usage, then return value, then required params. Every sentence adds value without redundancy.

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?

Given no output schema, it mentions returning the modified object. Schema covers all parameters. It provides partial update behavior and required fields. Lacks mention of the 'attachments' parameter, but schema handles that. Overall complete for a straightforward update 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 coverage is 100%, so the schema already documents all parameters. The description reinforces required parameters (id, project_id, list) but does not add meaning beyond the schema. It provides slightly above baseline by summarizing required parameters.

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 it updates an Inspection Checklist in a specified Project, using specific verb and resource. It distinguishes from siblings like 'update_checklist_inspection' by specifying it updates the entire checklist list, not individual inspection items.

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?

It provides clear when to use (updating existing checklist) and notes that only supplied fields are changed (PATCH semantics). It does not explicitly state when not to use or list alternatives, but the context is sufficient for a basic update operation.

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