Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Company Inspection Template Item

delete_company_inspection_template_item
DestructiveIdempotent

Permanently delete an item from a company inspection template. Specify the company, template, and item IDs.

Instructions

Deletes a Company Inspection Template Item for a specified Company. Use this to permanently delete the specified Inspections. This cannot be undone. Permanently removes the specified Inspections. This action cannot be undone. Required parameters: company_id, inspection_template_id, id. Procore API: Project Management > Inspections. Endpoint: DELETE /rest/v1.0/companies/{company_id}/inspection_templates/{inspection_template_id}/items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
inspection_template_idYesURL path parameter — the ID of the Company Inspection Template
idYesURL path parameter — company Inspection Template Item ID
Behavior4/5

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

Annotations already indicate destructiveHint=true. The description adds emphasis by stating 'cannot be undone' and 'permanently removes', which reinforces the permanent nature. No contradictions with annotations.

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

Conciseness4/5

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

The description is relatively concise but contains redundancy with repeated phrases like 'This cannot be undone' and 'Permanently removes'. Otherwise well-structured with key information upfront.

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?

For a simple delete operation with three required parameters and no output schema, the description is fully adequate. It conveys permanence, required inputs, and API reference, leaving no critical gaps.

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?

The input schema has full description coverage for all three parameters. The description only lists them as required, adding no additional meaning or context beyond the schema.

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 the tool deletes a Company Inspection Template Item using the verb 'Deletes' and specifies the resource and scope. It distinguishes from other tools by focusing on deletion and requiring specific IDs.

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?

The description explicitly warns that the action is permanent and cannot be undone, and lists required parameters. However, it does not mention when to use this tool versus alternative delete tools, leaving room for improvement.

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