Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Bulk Update WBS Codes

bulk_update_wbs_codes
Idempotent

Bulk update WBS codes with the same status in one request, avoiding repeated single-record calls. Uses project_id from config when omitted and returns modified codes on success.

Instructions

Bulk update WBS Codes with the same status. Prefer this over repeated single-record calls when handling many WBS codes at once. project_id defaults to the value set by procore_set_config when omitted. Returns the modified WBS code 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: project_id, ids, attributes. Procore API: Construction Financials > Work Breakdown Structure. Endpoint: PATCH /rest/v1.0/projects/{project_id}/work_breakdown_structure/wbs_codes/update_all

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesJSON request body field — wBS Code IDs
attributesYesJSON request body field — the attributes for this Work Breakdown Structure operation
project_idYesURL path parameter — unique identifier for the project.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

The description goes beyond the annotations by detailing the success return ('Returns the modified WBS code on success') and specific failure modes (401, 403, 404) with their causes. It also discloses that project_id defaults to the preconfigured value, which is not in the 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 packs action, guidance, defaults, return behavior, error handling, required params, API category, and endpoint into a tight paragraph with no filler. Every sentence earns its place.

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?

The description covers most practical aspects: what, when, defaults, success/error returns, and endpoint. However, the 'attributes' object's internal structure is left undefined, which is a notable gap for a complex bulk-update operation with no output schema.

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 meaningful context for project_id (defaults to procore_set_config value) and hints that attributes carries a status ('with the same status'), raising the score to 4.

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 a specific verb-object ('Bulk update WBS Codes') and clarifies scope ('with the same status'). It clearly distinguishes itself from single-record updates by explicitly recommending this tool for many WBS codes at once.

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?

The sentence 'Prefer this over repeated single-record calls when handling many WBS codes at once' explicitly states when to use this tool and names the alternative approach. It also notes the project_id default behavior, helping the agent decide when the parameter can be omitted.

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