Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Requisitions (Subcontractor Invoices) For Project

list_requisitions_subcontractor_invoices_for_project
Read-onlyIdempotent

Retrieve a paginated list of subcontractor invoices for a specified project. Filter by status, commitment, period, and more.

Instructions

Return a list of Requisitions (Subcontractor Invoices) on a specified project See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to enumerate Commitments when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Commitments. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API (v1.1): Construction Financials > Commitments. Endpoint: GET /rest/v1.1/requisitions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — elements per page, default 30
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__commitment_idNoQuery string parameter — commitment ID(s). Returns item(s) with the specified Commitment ID(s).
filters__period_idNoQuery string parameter — billing Period ID. Returns item(s) with the specified Billing Period ID.
filters__statusNoQuery string parameter — return item(s) with the specified Requisition (Subcontractor Invoice) status.
filters__created_atNoQuery string parameter — return item(s) created within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset
filters__origin_idNoQuery string parameter — origin ID. Returns item(s) with the specified Origin ID.
filters__is_lastNoQuery string parameter — setting this to true will return only the last item. Setting this to false will return all the items except the last one.
viewNoQuery string parameter — specifies which view (which attributes) of the resource is going to be present in the response.
Behavior3/5

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

Annotations already indicate read-only and idempotent behavior. The description adds that it returns a paginated JSON array with pagination metadata, which is useful. However, it inaccurately describes the result type as 'Commitments' instead of 'Requisitions', and does not disclose other behavioral traits like rate limits or endpoint details beyond the endpoint string.

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 relatively concise at 5 sentences, with a clear structure: purpose, link to filtering docs, usage case, return type, pagination info, required parameter, and API reference. The inclusion of the API version and endpoint is helpful but slightly wordy.

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

Completeness2/5

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

Given the complexity of 12 parameters and no output schema, the description does not fully explain what data is returned (only 'paginated JSON array of Commitments' without field details or pagination metadata format). The inaccuracy of calling results 'Commitments' further reduces completeness. The description lacks explanation of the view parameter and filter options beyond the schema.

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?

All 12 parameters are documented in the input schema with descriptions (100% coverage). The description does not add new semantic information beyond restating that project_id is required and page/per_page control pagination. No additional parameter details are provided.

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 list of Requisitions (Subcontractor Invoices) for a specified project. However, it later refers to the results as 'Commitments', which may cause confusion and detracts from precision.

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 a usage scenario: enumeration for paginated overview, finding IDs, or filtering. It mentions pagination and required parameter project_id, but does not explicitly exclude cases or mention alternative tools among siblings.

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