Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Drawing Set

delete_drawing_set
DestructiveIdempotent

Permanently removes a drawing set and associated drawings from a project. This action is irreversible.

Instructions

Delete a specified Drawing Set. Use this to permanently delete the specified Drawings. This cannot be undone. Permanently removes the specified Drawings. This action cannot be undone. Required parameters: project_id, id. Procore API: Project Management > Drawings. Endpoint: DELETE /rest/v1.0/projects/{project_id}/drawing_sets/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — iD of the drawing set
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description goes beyond by explicitly stating 'This cannot be undone' and 'Permanently removes the specified Drawings,' adding clear behavioral context about irreversibility. There is no contradiction 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.

Conciseness5/5

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

The description is four sentences long, all directly relevant. It front-loads the main action, then adds critical permanence information and ends with endpoint details. No wasted words or redundant information.

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?

For a simple delete operation, the description adequately covers the action, required parameters, and API location. It does not mention return values or error handling, but given the lack of output schema and the straightforward nature of the operation, this is acceptable.

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 100% coverage with descriptions for both parameters (project_id, id). The description merely lists them as required, which adds no new meaning beyond the schema. Baseline score of 3 is appropriate when schema fully documents 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 uses a specific verb ('Delete') and clearly identifies the resource ('Drawing Set'). It also explicitly states the action is permanent and cannot be undone, which unambiguously distinguishes it from other tools in the sibling list.

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

Usage Guidelines3/5

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

The description states to 'use this to permanently delete the specified Drawings' but provides no guidance on when not to use it or any alternatives. Given the extensive list of sibling delete tools, the lack of exclusion criteria or context on when this tool is appropriate is a notable gap.

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