Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Prime Contracts

list_prime_contracts
Read-onlyIdempotent

Retrieve a paginated list of prime contracts for a project. Use filters like status, vendor, or executed to narrow results.

Instructions

Returns a list of Prime Contracts for a given project. Use this to enumerate Prime Contracts when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Prime Contracts. 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 > Prime Contracts. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_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 architect name, contractor name, vendor name and custom fields data, whil...
filters__accounting_methodNoQuery string parameter — filter to unit or amount based contracts
filters__architect_idNoQuery string parameter — return item(s) with the specified Architect ID(s). These are Login Information IDs.
filters__contractor_idNoQuery string parameter — return item(s) with the specified Contractor ID(s). These are Vendor IDs.
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 declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds value by specifying paginated response behavior and metadata, which is consistent with annotations. No contradiction.

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 concise at about 5 sentences, but it has some redundancy (e.g., mentions pagination twice). It front-loads the main purpose and quickly provides actionable parameter info. Overall efficient, but could trim slight repetition.

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?

Given no output schema and 16 parameters, the description covers purpose, usage, and pagination. However, it does not describe the response structure beyond 'JSON array with pagination metadata' or mention the 'view' parameter that affects response attributes. This leaves gaps for an agent needing detailed output knowledge.

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% with detailed parameter descriptions. The description only reiterates that company_id and project_id are required and mentions page/per_page for pagination, adding minimal meaning beyond the schema. Baseline 3 is appropriate.

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 Prime Contracts for a given project, with a specific verb ('Returns') and resource ('Prime Contracts'). It is project-scoped, which helps distinguish from potential siblings like 'list_all_prime_contracts', though no explicit comparison is made.

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 usage scenarios: 'enumerate Prime Contracts when you need a paginated overview, to find IDs, or to filter by query parameters.' It also mentions required parameters (company_id, project_id) but does not explicitly state when not to use this tool or list alternatives.

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