Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project WBS Codes

list_project_wbs_codes
Read-onlyIdempotent

Enumerate paginated Work Breakdown Structure codes for a project. Filter by status, updated date, scope, or group by contract.

Instructions

All Work Breakdown Structure codes for a given project. Use this to enumerate Work Breakdown Structure records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Work Breakdown Structure records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Construction Financials > Work Breakdown Structure. Endpoint: GET /rest/v1.0/projects/{project_id}/work_breakdown_structure/wbs_codes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
can_select_divisionsNoQuery string parameter — if true, will include WBS Codes with division segment items. Default is true.
required_segmentsNoQuery string parameter — the required segments for this Work Breakdown Structure operation
filters__status__NoQuery string parameter — filter results to only return codes with the included statuses. Options are 'active' or 'inactive'. Defaults to returning all results.
filters__updated_atNoQuery string parameter — filter results to only return codes that were updated within the range of the two specified ISO 8601 timestamps separated by the ... delimiter.
scopeNoQuery string parameter — filter results to only return codes that match the specified WBS scope.
queryNoQuery string parameter — searches the WBS code and description values and returns results sorted in descending order of relevance to the search query.
group_typeNoQuery string parameter — along with 'group_id', groups WBS codes by the specified group type and group ID. Only supported option is 'contract'.
group_idNoQuery string parameter — along with 'group_type', groups WBS codes by the specified group type and group ID. Only supported option is a contract ID.
hide_not_in_groupNoQuery string parameter — if true, will hide WBS codes that are not in the specified 'group_type' and 'group_id'. Default is true. If false, WBS codes in the specified group will be returned first followed by WBS codes not ...
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already indicate read-only, safe operation. Description adds valuable context about pagination, return type (JSON array), and endpoint, enhancing behavioral understanding beyond 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?

Description is concise and well-structured: purpose, usage, pagination details, required parameter, and API reference. Every sentence adds value.

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?

Adequately complete for a list operation, covering pagination and filtering. Missing output schema details but description states returns JSON array. Could be more explicit about output fields.

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

Parameters3/5

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

Schema covers all parameters with descriptions (100% coverage). Description merely repeats required project_id and pagination control, adding no new semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it lists WBS codes for a given project, with specific use cases like paginated overview and filtering. However, it does not explicitly differentiate from sibling tools like list_wbs_codes, which may cause confusion.

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

Usage Guidelines3/5

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

Provides clear context for when to use (paginated overview, find IDs, filter), but no exclusion guidance or mention of alternatives like list_wbs_code_ids when only IDs are needed.

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