Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Asset

delete_asset_company
DestructiveIdempotent

Delete a company asset and all associated attachments and change history. Use cascade=true to remove descendant assets atomically; otherwise, assets with children return a 409 conflict.

Instructions

Deletes a company asset and all its associated attachments and change history. If the asset has descendants in the asset hierarchy, the caller must opt in with ?cascade=true; otherwise the request fails with HTTP 409 and the response body lists the blocking descendants so the UI can prompt for confirmation. Confirm the target id with the matching show or list tool before calling. company_id defaults to the value set by procore_set_config when omitted, and asset_id must identify an existing parent record — resolve it with the matching list tool first. Permanently removes the asset. 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: company_id, asset_id. Procore API (v2.0): Core > Assets. Endpoint: DELETE /rest/v2.0/companies/{company_id}/assets/{asset_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cascadeNoQuery string parameter — when true, also delete every descendant asset in the subtree atomically. Defaults to false; required when the asset has children.
asset_idYesURL path parameter — unique identifier for the asset
company_idYesURL path parameter — unique identifier for the company.
Accept-LanguageNoJSON request body field — locale for localized response messages (for example: en, fr-FR, pseudo)
Behavior5/5

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

Beyond the annotations (destructiveHint true, idempotentHint true), the description discloses critical behavior: cascading deletion with 409 and blocking descendant list, permanent removal with no undo, repeat call returning 404, common error payloads (401/403/404), and the company_id default from procore_set_config. 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?

Every sentence earns its place: scope, cascade behavior, preconditions, defaults, permanence, error handling, required parameters, and endpoint are all covered. The description is dense but not wasteful, appropriately sized for a destructive operation.

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?

With no output schema, the description still covers the tool's purpose, cascade semantics, parameter resolution, failure modes, and API location. It clearly communicates what happens on success (permanent removal) and on failure, making it operationally complete for an agent.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning beyond the schema: company_id defaults from procore_set_config when omitted (though the schema marks it required), asset_id must reference an existing parent record and should be resolved via list tool, and cascade defaults to false. This contextual information pushes it above baseline.

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 'Deletes a company asset and all its associated attachments and change history,' using a specific verb and resource. It clearly identifies the company scope and distinguishes from other delete tools in the sibling list (e.g., delete_asset_project, delete_equipment_company).

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

Usage Guidelines5/5

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

It provides explicit preconditions: confirm the target id with the matching show/list tool before calling, resolve asset_id with the matching list tool, and opt in with cascade=true when descendants exist. It also explains the 409 failure mode and the need for UI confirmation, guiding the agent on when and how to invoke the tool safely.

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