Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get All Purchase Orders

get_all_purchase_orders
Read-onlyIdempotent

Fetch paginated purchase order lists from Procore with filters for vendor, status, dates, and more. Select view types to control response detail.

Instructions

Returns a paginated list of purchase orders with filtering and sorting options. Supports multiple view types: Normal (default), Short, Compact, Extended, Mobile, and Id. Results can be filtered by associated document IDs, labels, and vendors. Use this when you already know which purchase order 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 purchase order. 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/purchase_orders

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. For Ids view the maximum page size is 5000.
company_idYesURL path parameter — the company identifier
project_idYesURL path parameter — the project identifier
filters__idNoQuery string parameter — comma-separated list of purchase order IDs to filter by
filters__labelsNoQuery string parameter — filter results by labels
filters__searchNoQuery string parameter — filter results by search
filters__statusNoQuery string parameter — filter by purchase order status(es)
filters__vendorNoQuery string parameter — filter results by vendor
filters__columnsNoQuery string parameter — the columns to include in the response
overdue_po_linesNoQuery string parameter — filter for overdue purchase order lines
filters__po_guidsNoQuery string parameter — comma-separated list of purchase order GUIDs to filter by
filters__origin_idNoQuery string parameter — comma-separated list of purchase order Origin IDs to filter by
filters__created_atNoQuery string parameter — the date range string for purchase order creation dates. Format: [YYYY-MM-DD...YYYY-MM-DD] (e.g. [2026-01-01...2026-12-31])
filters__updated_atNoQuery string parameter — the updated date range string for purchase order modification dates. Format: [YYYY-MM-DD...YYYY-MM-DD] (e.g. [2026-01-01...2026-12-31])
filters__property_keyNoQuery string parameter — the document property key for filtering
filters__property_valueNoQuery string parameter — the document property value for filtering
filters__include_deletedNoQuery string parameter — filter to include or exclude deleted purchase orders
filters__associated_doc_idsNoQuery string parameter — associated document IDs
filters__include_fully_shippedNoQuery string parameter — filter to include or exclude fully shipped purchase orders. When false (default), only POs with remaining quantity to ship are returned.
filters__include_fully_receivedNoQuery string parameter — filter to include or exclude fully received purchase orders. When true (default), All purchase orders are returned.
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's 'Read-only' line adds little. It does add useful context about default company_id/project_id from procore_set_config and common HTTP error codes. However, the false claim 'Returns a single JSON object describing the purchase order' is a significant behavioral misstatement that undermines transparency.

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 reasonably organized and front-loaded with the main verb+resource. However, it contains redundant statements (read-only, required parameters, view types already in schema) and includes a contradictory 'single JSON object' sentence that should have been caught. It earns a middle score for being informative but not tight.

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?

For a tool with 23 parameters, no output schema, and good annotations, the description covers pagination, filtering, views, defaults, error handling, and endpoint path. But the incorrect return-type statement creates a serious gap in understanding the actual response shape. It also lacks explicit guidance on pagination semantics beyond what schema provides.

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%, so each parameter is already described in the input schema. The description's mentions of view types and filterable fields (labels, vendors, associated document IDs) merely echo existing schema enums and descriptions without adding new meaning. It repeats required parameters without deepening understanding.

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 opens with a clear, specific verb+resource statement: 'Returns a paginated list of purchase orders with filtering and sorting options.' However, it later states 'Returns a single JSON object describing the purchase order,' which contradicts the list semantics and confuses the tool's actual purpose. Despite this inconsistency, the core purpose is still identifiable.

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 description offers only 'Use this when you already know which purchase order you want and need its full field set,' which is misleading because this is a list endpoint rather than a single-record retrieval. It does not distinguish this tool from closely related siblings like list_of_purchase_order_contracts or get_all_purchase_order_line_items, and provides no 'when not to use' 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