Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Segment Items

list_project_segment_items
Read-onlyIdempotent

Retrieve paginated Work Breakdown Structure records for a project segment. Filter by legacy cost code, sub job, or active status to find specific items.

Instructions

List Segment Items for a specific segment. 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, segment_id. Procore API: Construction Financials > Work Breakdown Structure. Endpoint: GET /rest/v1.0/projects/{project_id}/work_breakdown_structure/segments/{segment_id}/segment_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
segment_idYesURL path parameter — unique identifier of the segment
legacy_sub_job_idNoQuery string parameter — used to filter legacy cost codes by sub job. Default will filter by project.
legacy_cost_code_idNoQuery string parameter — unique identifier of the legacy cost code
include_action_policyNoQuery string parameter — include_action_policy
only_active_itemsNoQuery string parameter — the only active items for this Work Breakdown Structure operation
with_descendant_countsNoQuery string parameter — with_descendant_counts
include_sub_job_cost_codesNoQuery string parameter — include_sub_job_cost_codes
with_sub_job_cost_codes_countNoQuery string parameter — used to include the count of cost codes that can be used to create wbs codes for each sub job. ONLY supported by sub jobs.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the tool's safety and idempotency are covered. The description adds context about pagination and filtering but no additional behavioral traits beyond what annotations provide.

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 concise with four sentences, front-loading the purpose, use cases, return information, parameters, and API details. Every sentence is meaningful and efficient, with no redundancy.

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?

Given the complexity (11 parameters, no output schema, pagination), the description covers main usage and mentions pagination metadata in the response. It could be more complete by describing the response structure, but it is adequate for an experienced user.

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% with descriptions for all 11 parameters. The description adds value by mentioning pagination control with page and per_page and that the response includes pagination metadata, going beyond the schema but not significantly.

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 clearly states 'List Segment Items for a specific segment' with a specific verb and resource. It also explains use cases like enumerating Work Breakdown Structure records, finding IDs, or filtering by query parameters, which distinguishes it from sibling tools like list_company_segment_items.

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?

The description provides clear context on when to use the tool (enumerate WBS records, find IDs, filter) and mentions required parameters. However, it does not explicitly state when not to use it or compare with alternatives such as list_company_segment_items, which would improve guidance.

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