Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Actual Production Quantity

update_actual_production_quantity

Update the installed quantity for an existing field productivity record in a Procore project. Modify quantity, description, crew, or location as needed.

Instructions

Update Actual Production Quantity associated with the specific Project. Use this to update an existing Field Productivity records (only the supplied fields are changed). Updates the specified Field Productivity records and returns the modified object on success. Required parameters: project_id, id, quantity. Procore API: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/projects/{project_id}/actual_production_quantities/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Field Productivity resource
descriptionNoJSON request body field — the description of the Actual Production Quantity
quantityYesJSON request body field — amount installed
crew_idNoJSON request body field — the ID of the crew for the Actual Production Quantity
location_idNoJSON request body field — the Location ID for the Actual Production Quantity
Behavior3/5

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

Annotations (readOnlyHint=false, destructiveHint=false) already signal this is a write operation that is not destructive. The description adds value by clarifying it's a partial update (only supplied fields changed) and states it returns the modified object on success. No contradiction with annotations.

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 concise with three sentences: purpose, partial update behavior, and required parameters/API endpoint. No superfluous text. Information is front-loaded.

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?

The description covers the basic behavior (partial update, returns modified object) and lists required parameters. However, it does not mention error handling, required permissions, or response format beyond 'modified object'. For a CRUD update, this is minimally adequate but lacks additional context for an AI agent.

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% description coverage. The description reinforces the meaning of 'only the supplied fields are changed', indicating that parameters beyond the required ones are optional and will be updated only if provided. This adds semantic context beyond the individual parameter descriptions.

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 the verb 'update' and the resource 'Actual Production Quantity' associated with a project. It explains that it updates existing Field Productivity records and that only supplied fields are changed. However, it does not explicitly differentiate from sibling tools like bulk_update_actual_production_quantities or create_actual_production_quantity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context that this tool is for updating existing records with partial updates (only supplied fields are changed). It lists required parameters. However, it does not specify when to use this tool versus alternatives (e.g., bulk updates) or mention any prerequisites or limitations.

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