Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Manual Holds For A Given Invoice

list_manual_holds_for_a_given_invoice
Read-onlyIdempotent

Retrieve all manual holds for a specified invoice, with paginated results and filtering by project and invoice IDs.

Instructions

Return a list of all manual holds for a given invoice. Use this to enumerate Invoices when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Invoices. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id, invoice_id. Procore API: Construction Financials > Invoices. Endpoint: GET /rest/v1.0/projects/{project_id}/payment_readiness/manual_holds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
invoice_idYesQuery string parameter — unique identifier of the invoice to retrieve manual holds
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior2/5

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

Annotations already declare the tool as read-only. The description adds pagination details but incorrectly states the response contains invoices rather than manual holds, undermining trust.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively short but contains inaccuracies. The first part is misleading, and the API path inclusion adds unnecessary noise.

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?

Without an output schema, the description should correctly describe the response. It mentions pagination but misidentifies the returned data as invoices instead of manual holds, leaving critical gaps.

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 parameters are well-documented. The description redundantly lists required parameters and adds API endpoint context, adding minimal extra meaning.

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 tool name and initial sentence clearly indicate listing manual holds for an invoice. However, the description then misstates the purpose as enumerating invoices, causing confusion.

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?

No guidance on when to use this tool versus alternatives. The description incorrectly suggests it is for enumerating invoices, which could lead to misuse.

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