Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show All Prime Change Order Batches

show_all_prime_change_order_batches
Read-onlyIdempotent

Retrieve prime change order batches filtered by project, status, date, or IDs. Results are paginated for easy access.

Instructions

Returns all Prime Change Order Batches for the specified Project. Use this to fetch the full details of a specific Prime Contracts by its identifier. Returns a paginated JSON array of Prime Contracts. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Construction Financials > Prime Contracts. Endpoint: GET /rest/v1.0/projects/{project_id}/prime_change_order_batches

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
sortNoQuery string parameter — direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter.
filters__idNoQuery string parameter — filter results by Change Order Batch ID
filters__change_order_idNoQuery string parameter — filter results by Change Order ID
filters__contract_idNoQuery string parameter — filter results by Contract ID
filters__updated_atNoQuery string parameter — return item(s) within a specific updated at iso8601 datetime range
filters__statusNoQuery string parameter — array of Status. Return item(s) with the specified status.
filters__status__notNoQuery string parameter — array of Status. Return item(s) that does not have specified status.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the response is a paginated JSON array with metadata, which is useful but does not contradict annotations. No additional behavioral traits are disclosed.

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 concise but includes a redundant and confusing sentence about 'specific Prime Contracts.' This wastes space and could be removed or corrected.

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?

With 10 parameters and no output schema, the description only covers the main purpose and pagination. It fails to explain filter parameters, return structure beyond pagination metadata, or how the tool fits into the broader API context. More detail is needed for completeness.

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 baseline is 3. The description mentions project_id as required and explains pagination (page, per_page), but does not elaborate on filter or sort parameters, leaving their meaning to the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it 'Returns all Prime Change Order Batches for the specified Project,' which is clear. However, it also says 'Use this to fetch the full details of a specific Prime Contracts by its identifier,' which is inaccurate and misleading, as the tool returns all batches, not a specific contract. This reduces clarity.

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 provides no guidance on when to use this tool versus siblings like 'show_prime_change_order_batch' or 'show_all_prime_change_orders.' It does not mention when not to use it or any 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