Skip to main content
Glama
TylerIlunga

Procore MCP Server

List All Actual Production Quantities

list_all_actual_production_quantities
Read-onlyIdempotent

Retrieve actual production quantities for a project. List field productivity records with pagination and optional filters to find specific records or IDs.

Instructions

Return a list of all Actual Production Quantities for a specified Project. Use this to enumerate Field Productivity records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Field Productivity records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Field Productivity. Endpoint: GET /rest/v1.0/projects/{project_id}/actual_production_quantities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
filters__unit_of_measureNoQuery string parameter — return item(s) with the specified unit of measure.
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 `YYY...
filters__timesheet_idNoQuery string parameter — timesheet ID. Returns item(s) with the specified Timesheet ID.
filters__crew_idNoQuery string parameter — crew ID. Returns item(s) with the specified Crew ID.
filters__location_idNoQuery string parameter — location ID. Returns item(s) with the specified Location ID or a range of Location IDs.
filters__dateNoQuery string parameter — returns item(s) within the specified ISO 8601 datetime range.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
pageNoQuery string parameter — page number for paginated results (default: 1)
Behavior5/5

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

Adds value beyond annotations by describing pagination behavior (page/per_page, metadata) and endpoint details, complementing the readOnlyHint and idempotentHint.

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?

Three sentences: purpose, usage/return, pagination/required params. Well-structured, front-loaded, no fluff.

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

Completeness5/5

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

Covers essential context: paginated list, filter capability, required param. Despite 10 params, schema fills detail; description is sufficient for a list endpoint.

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 has 100% coverage, so baseline is 3. Description mentions required parameter and pagination parameters but does not add significant meaning beyond schema descriptions.

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 'Return' and resource 'list of all Actual Production Quantities for a specified Project', distinguishing it from siblings like 'show_actual_production_quantity' and bulk operations.

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?

Explicitly tells when to use the tool (enumerate paginated overview, find IDs, filter) but does not mention when not to use it 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