Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company WBS Segment

update_company_wbs_segment
Idempotent

Update an existing company-level WBS segment by sending only the fields you want to change. Use to modify segment name or project-level permission flags via the Procore API.

Instructions

Update company level WBS Segment. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "segment" in the request payload for you. 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. Returns the modified company WBS segment on success. 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: PATCH /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
nameNoJSON request body field — segment Name
company_idYesURL path parameter — unique identifier for the company.
segment_item_list_idNoQuery string parameter — segment Item List ID
project_can_delete_origin_companyNoJSON request body field — whether Segment Items inherited from the company-level are able to be deleted from a Project.
project_can_modify_origin_projectNoJSON request body field — whether project-specific Segment Items are able to be added/edited/removed from a Project.
Behavior5/5

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

The description discloses partial-update semantics, payload nesting, company_id defaulting, error payload shapes with common HTTP statuses, and the success return. This adds significant behavioral detail beyond the existing 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 dense but each sentence conveys a distinct piece of actionable information: purpose, partial-update behavior, field passing convention, defaults, id resolution, return value, errors, and endpoint. No fluff.

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 six parameters and no output schema, the description nevertheless covers the purpose, usage steps, parameter specifics, error scenarios, and return value, making it complete for an agent to select and invoke the tool. The only minor gap is not naming the list tool, but it clearly points to one.

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 schema already covers all six parameters with 100% coverage, so the baseline is 3. The description adds value by explaining the company_id default from procore_set_config and that id must be resolved first, plus the instruction to send top-level fields for the nested segment payload.

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 'Update company level WBS Segment,' a specific verb and resource. The endpoint and HTTP method further specify the action, and 'company level' differentiates it from project-level or segment-item tools among siblings.

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 tells the agent to send only changed fields and to resolve the id via 'the matching list tool first,' providing a clear precondition. It does not explicitly name the list tool or state when not to use this tool, but the context makes it clear.

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