Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete WBS Segment

delete_wbs_segment
DestructiveIdempotent

Permanently delete a work breakdown structure (WBS) segment from a Procore company. Verify the segment ID with the list tool first to ensure a successful deletion.

Instructions

Deletes a WBS segment for the specified Procore company. 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 id must identify an existing parent record — resolve it with the matching list tool first. Permanently removes the WBS segment. 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, id. Procore API: Construction Financials > Work Breakdown Structure. Endpoint: DELETE /rest/v1.0/companies/{company_id}/work_breakdown_structure/segments/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Work Breakdown Structure resource
company_idYesURL path parameter — unique identifier for the company.
segment_item_list_idNoQuery string parameter — segment Item List ID
Behavior5/5

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

Annotations already mark destructiveHint=true, but the description adds that the segment is permanently removed, cannot be undone, a repeat call returns 404, and common error statuses (401, 403, 404) with meanings. This goes well beyond the annotation flags.

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

Conciseness3/5

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

The description is a single dense paragraph that repeats the id-resolution guidance twice ('Confirm the target id...' and 'resolve it with the matching list tool first'), which adds redundancy. The rest is valuable but could be structured more tightly.

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 destructive tool, it covers prerequisites, permanence, repeat-call behavior, and error statuses. However, it doesn't mention the success response format (e.g., 204 No Content), which is a minor gap but not critical for execution.

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?

The description clarifies that company_id defaults to procore_set_config when omitted and that id must resolve to an existing parent record via the list tool, adding operational meaning beyond the schema's simple field descriptions. It also states required 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 opens with 'Deletes a WBS segment for the specified Procore company,' clearly identifying the verb and resource. It further specifies the API endpoint and confirms the permanent nature, distinguishing it from other delete tools targeting different resources.

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 instructs the agent to confirm the target id with the matching show or list tool before calling and to resolve id with the matching list tool first. This provides clear preconditions, though it doesn't explicitly discuss when not to use the tool or alternatives to deletion.

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