Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get All Shipment Line Items

get_all_shipment_line_items
Read-onlyIdempotent

Fetch paginated shipment line items across all shipments in a Procore project. Filter by vendor, status, destination, or date to retrieve full field sets for specific line items.

Instructions

Returns a paginated list of shipment line items across all shipments in the project. Supports view types: Normal (default), Mobile, and Id. The Mobile view also includes the remaining-to-be-received quantity. Use this when you already know which shipment line item you want and need its full field set. company_id and project_id default to the values set by procore_set_config when omitted. Returns a single JSON object describing the shipment line item. Read-only — it changes nothing in Procore. 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, project_id. Procore API (v2.0): Resource Management > Materials Management. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/materials_mgmt/shipments/line_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — sort results by field. Prefix with '-' for descending order (e.g. '-created_at').
viewNoQuery string parameter — response detail level. Use 'normal' for standard fields or 'extended' for all fields
per_pageNoQuery string parameter — the page size between 1 and 100.
company_idYesURL path parameter — the company identifier
project_idYesURL path parameter — the project identifier
filters__idNoQuery string parameter — comma-separated list of shipment line item GUIDs to filter by
filters__labelsNoQuery string parameter — comma-separated list of shipment tags to filter by
filters__searchNoQuery string parameter — filter results by search
filters__statusNoQuery string parameter — filter by shipment status(es)
filters__vendorNoQuery string parameter — the vendor associated with the shipments
filters__columnsNoQuery string parameter — the columns to include in the response
filters__updated_atNoQuery string parameter — date range for filtering shipment line items based on their last updated date. Format: [YYYY-MM-DD...YYYY-MM-DD] (e.g. [2026-01-01...2026-12-31])
filters__destinationNoQuery string parameter — comma-separated list of shipment destinations to filter by
filters__property_keyNoQuery string parameter — the property key for filtering
filters__shipment_idsNoQuery string parameter — comma-separated list of shipment GUIDs to filter by
filters__material_typeNoQuery string parameter — the material type to filter by
filters__shipment_typeNoQuery string parameter — comma-separated values (filters[shipment_type]). Filters shipment.subtype_id, not document shipment_type_id / .
filters__property_valueNoQuery string parameter — the property value for filtering
filters__estimated_delivery_atNoQuery string parameter — date range for filtering shipments based on their delivery date. Format: [YYYY-MM-DD...YYYY-MM-DD] (e.g. [2026-01-01...2026-12-31])
filters__material_property_keyNoQuery string parameter — the material property key for filtering
filters__associated_document_idsNoQuery string parameter — comma-separated list of associated document IDs to filter by
filters__material_property_valueNoQuery string parameter — the material property value for filtering
Behavior4/5

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

The description adds significant context beyond annotations, including pagination, view types, default parameter behavior, and common HTTP error scenarios. It is consistent with the readOnlyHint and destructiveHint annotations.

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

Conciseness3/5

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

The description is structured with useful context but is verbose and contains redundant statements like 'Required parameters: company_id, project_id' (already in schema) and a contradictory 'single JSON object' line that detracts from its conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers pagination, view types, defaults, errors, endpoint, and required parameters, making it fairly complete for a complex 23-parameter tool. However, the inconsistent return-type statement leaves ambiguity about whether the tool returns a list or a single object.

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% for all 23 parameters. The description adds valuable meaning about view types (Normal, Mobile, Id), the Mobile view's extra field, and defaulting of company_id/project_id from procore_set_config.

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 returns a paginated list of shipment line items across all shipments, which is a specific verb+resource+scope. However, the contradictory 'Returns a single JSON object' and 'Use this when you already know which shipment line item you want' lines obscure the exact purpose and could mislead.

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

Usage Guidelines2/5

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

The 'Use this when' guidance is misplaced for a list-all tool and provides no explicit exclusions or alternatives. It does not mention when to prefer this over similar tools like get_all_line_items_for_a_specific_shipment.

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