Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Checklist Section

update_checklist_section

Update an existing checklist section (inspection section) by providing the list ID, section ID, project ID, and section data. Only supplied fields are changed.

Instructions

This is a deprecated endpoint. 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: list_id, id, project_id, section. Procore API: Project Management > Inspections. Endpoint: PATCH /rest/v1.0/checklist/lists/{list_id}/sections/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesURL path parameter — unique identifier of the list
idYesURL path parameter — checklist Section ID
project_idYesJSON request body field — the ID of the Project the Section belongs to
sectionYesJSON request body field — section object
Behavior3/5

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

Annotations indicate it is a write operation (readOnlyHint=false) and non-destructive. The description adds that only supplied fields are changed (partial update) and returns the modified object. However, the misstatement about 'Inspections' undermines trust. Adequate but not fully reliable.

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?

Three sentences: first flags deprecation (important), second describes update behavior, third lists API info. Could be more concise and avoid redundancy. Adequate but not excellent.

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?

No output schema, so the description should clarify return structure; it says 'returns the modified object' but does not detail it. The nested 'section' parameter is not explained. Missing permissions and error conditions. Incomplete given the tool's complexity.

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% with clear parameter descriptions. The description merely lists required parameters, adding no new meaning beyond the schema. Baseline score of 3 applies.

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 states 'update an existing Inspections' but the tool is for updating a checklist section, creating confusion. The verb and resource are clear from the name, but the description contradicts it, reducing clarity.

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 notes the endpoint is deprecated but provides no guidance on when to use this tool versus alternatives like create_checklist_section or delete_checklist_section. Missing when-not and alternatives.

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