Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Checklist Section

delete_checklist_section
DestructiveIdempotent

Permanently delete a checklist section using its list ID, section ID, and project ID. This action cannot be undone.

Instructions

This is a deprecated endpoint. Use this to permanently delete the specified Inspections. This cannot be undone. Permanently removes the specified Inspections. This action cannot be undone. Required parameters: list_id, id, project_id. Procore API: Project Management > Inspections. Endpoint: DELETE /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_idYesQuery string parameter — unique identifier for the project.
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description repeats 'cannot be undone' twice, reinforcing the destructive nature, but adds no new behavioral insight beyond what annotations provide.

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

Conciseness2/5

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

The description is repetitive ('permanently delete', 'cannot be undone' said twice) and contains a factual error (states Inspections instead of sections). It is not well-structured or concise.

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?

The description lacks context about what a checklist section is, what happens to its contents upon deletion, or any side effects. The deprecation notice is useful but incomplete for a deletion tool with no output schema.

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?

Input schema has 100% description coverage with clear parameter descriptions. The description merely lists required parameters without adding meaning or context beyond the schema, so it meets the baseline.

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

Purpose1/5

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

The description states that the tool deletes 'Inspections' but the tool name and title refer to 'sections', creating a significant inconsistency. This misidentification undermines clarity about what the tool actually does.

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 mentions the endpoint is deprecated but provides no guidance on when to use this tool versus alternatives (e.g., a newer version). No explicit use cases or exclusions are given.

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