Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project WBS Task Codes

list_project_wbs_task_codes
Read-onlyIdempotent

Retrieve paginated Work Breakdown Structure task codes for a project to enumerate field productivity records and find IDs, with support for labor, equipment, or both types.

Instructions

All Work Breakdown Structure task codes for a given project, sorted by flat code. NOTE, this endpoint is currently in the experimental stage and is subject to change. Use this to enumerate Field Productivity records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Field Productivity records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Field Productivity. Endpoint: GET /rest/v1.0/projects/{project_id}/task_codes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
typeNoQuery string parameter — type of task codes to return
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
pageNoQuery string parameter — page number for paginated results (default: 1)
serializer_viewNoQuery string parameter — controls which Task Code blueprint is used to serialize the data. This defaults to `task_code_entity`, but `id_only` is also valid. Errors may be generated if requesting a serializer view that is n...
viewNoQuery string parameter — controls which Task Code blueprint is used to serialize the data. This defaults to `task_code_entity`, but `id_only` is also valid. Errors may be generated if requesting a serializer view that is n...
filtersNoQuery string parameter — filters for wbs task codes
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds that it is paginated, requires project_id, and is experimental. No contradictions.

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

Conciseness4/5

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

The description is concise and structured, covering purpose, usage, pagination, required params, and API details. It is efficient but could be slightly more streamlined.

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?

With no output schema, the description mentions 'Returns a paginated JSON array', which is sufficient. It also includes endpoint, experimental note, and required params. Fairly complete for the complexity.

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 coverage is 100%, with all 7 parameters well-described. The description repeats the required parameter but adds no additional semantic detail 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?

The description clearly states it lists WBS task codes for a project, sorted by flat code. It specifies the resource and action, though it doesn't explicitly differentiate from sibling tools.

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?

The description provides guidance to use it for enumerating Field Productivity records, finding IDs, and filtering. It also notes the experimental stage, but lacks explicit 'when not to use' or alternative tool references.

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