Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete A Classification

delete_a_classification
DestructiveIdempotent

Delete a project's work classification permanently using its ID. Requires project ID and classification ID; the action cannot be undone.

Instructions

Deleting a classification associated with the specified project. Confirm the target id with the matching show or list tool before calling. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Permanently removes the classification. This cannot be undone, and a repeat call returns 404. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, id. Procore API: Company Admin > Company Settings. Endpoint: DELETE /rest/v1.0/projects/{project_id}/work_classifications/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — id of the classification
project_idYesURL path parameter — unique identifier for the project.
Behavior5/5

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

Beyond the annotations (destructiveHint: true, etc.), the description discloses irreversibility ('Permanently removes... cannot be undone'), repeat-call behavior (404), and error semantics (401/403/404 with an error payload). This adds substantial value over the structured data.

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 compact despite covering many facets (action, preconditions, defaults, consequences, errors, required params, endpoint). Every sentence contributes, though it is slightly dense.

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 delete tool with only two parameters and no output schema, the description covers all necessary context: purpose, prerequisites, parameter defaults, error behavior, irreversibility, and the API endpoint. No significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the baseline is 3. The description adds meaning by noting that project_id defaults to the procore_set_config value and that id must reference an existing parent record, which is not in 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 opens with 'Deleting a classification associated with the specified project,' which uses a specific verb, resource, and scope. This clearly distinguishes it from sibling tools like list_all_classifications, create_classification, and update_classification.

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 explicitly instructs to 'Confirm the target id with the matching show or list tool before calling' and explains that id must resolve to an existing parent record. This provides clear usage context and prerequisites, though it does not name the exact list/show sibling tool.

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