Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Commitment Contracts

list_commitment_contracts
Read-onlyIdempotent

Retrieve a paginated list of commitment contracts for a project. Filter by type, status, vendor, or accounting method to find specific commitments.

Instructions

Returns a list of Commitment Contracts for a given project. 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: company_id, project_id. Procore API (v2.0): Construction Financials > Commitments. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/commitment_contracts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
viewNoQuery string parameter — specifies which view (which attributes) of the resource is going to be present in the response. The extended view includes vendor name and custom fields data, while the default view does not.
filters__include_deletedNoQuery string parameter — use 'only' to return only deleted resources. Use 'with' to return deleted and undeleted resources.
filters__accounting_methodNoQuery string parameter — filter to unit or amount based contracts
filters__typeNoQuery string parameter — filter based on what type of commitment contract it is.
filters__created_atNoQuery string parameter — filter based on the created_at time.
filters__deleted_atNoQuery string parameter — filter based on the deleted_at time.
filters__idNoQuery string parameter — return item(s) with the specified ID(s).
filters__signature_requiredNoQuery string parameter — filter based on whether a signature is required.
filters__statusNoQuery string parameter — filter to specific statuses. For Work Order Contracts: Draft, Out For Bid, Out For Signature, Approved, Complete, Terminated, Void. For Purchase Order Contracts: Draft, Processing, Submitted, Part...
filters__updated_atNoQuery string parameter — filter based on the updated_at time.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor ID(s).
filters__executedNoQuery string parameter — filter based on whether a contract is executed.
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, etc. The description adds behavioral context: paginated result, pagination metadata, and endpoint details. No contradictions. It complements annotations without repeating them.

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 four sentences, each serving a clear purpose: purpose, use cases, pagination guidance, and required parameters/API info. No unnecessary words, front-loaded with the main purpose.

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 (16 parameters, 4 enums) and no output schema, the description covers the essential use: pagination, filtering, and required IDs. It mentions pagination metadata in response. Could be slightly improved by mentioning default sorting, but sufficient.

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?

Input schema has 100% coverage, so baseline is 3. The description adds value by summarizing required parameters (company_id, project_id) and explaining pagination parameters (page, per_page) and their effect, which goes beyond what the schema provides.

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 the verb ('returns a list') and resource ('Commitment Contracts for a given project'). The title and description distinguish it from sibling tools like 'list_commitments' by specifying 'Commitment Contracts', indicating a different resource.

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 explicitly defines when to use the tool: 'when you need a paginated overview, to find IDs, or to filter by query parameters.' It also explains pagination usage. However, it does not provide guidance on when not to use it or mention alternatives like 'show_commitment_contract' for single records.

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