Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Bid Package

update_bid_package

Modify an existing bid package by updating fields like due date, email/web messages, title, and optional parameters. Only supplied fields are changed, returning the updated object.

Instructions

Update Bid Package. Use this to update an existing Bid Management records (only the supplied fields are changed). Updates the specified Bid Management records and returns the modified object on success. Required parameters: project_id, id, bid_due_date, bid_email_message, bid_web_message, title. Procore API: Preconstruction > Bid Management. Endpoint: PATCH /rest/v1.0/projects/{project_id}/bid_packages/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Bid Management resource
accept_post_due_submissionsNoJSON request body field — accepts bid post due submissions
bid_due_dateYesJSON request body field — bid due date in YYYY-MM-DD format
bid_email_messageYesJSON request body field — bid package email information details
bid_web_messageYesJSON request body field — bid package bidding instructions
titleYesJSON request body field — bid package title
accounting_methodNoJSON request body field — bid package accounting method, either 'amount' or 'unit'
bid_submission_confirmationNoJSON request body field — bid Package submission confirmation text
anticipated_award_dateNoJSON request body field — anticipated award date
numberNoJSON request body field — bid package number
distribution_idsNoJSON request body field — array of User IDs who will be on the bid package's distribution list
blind_biddingNoJSON request body field — blind bidding enabled
pre_bid_walk_through_dateNoJSON request body field — scheduled pre-bid walkthrough date
pre_bid_walk_through_notesNoJSON request body field — pre-bid walkthrough notes
enable_prebid_walkthroughNoJSON request body field — pre-bid walkthrough enabled
manager_idNoJSON request body field — login Information ID for Manager
require_ndaNoJSON request body field — require Non-Disclosure Agreement
display_project_nameNoJSON request body field — display project name
prostore_file_idsNoJSON request body field — array of Procore File IDs for Non-Disclosure Agreement
enable_public_discoveryNoJSON request body field — whether the bid package is discoverable by the public
pre_bid_meeting_locationNoJSON request body field — location for the pre-bid meeting
pre_bid_meeting_dateNoJSON request body field — date and time for the pre-bid meeting in UTC (ISO 8601 format)
pre_bid_meeting_online_linkNoJSON request body field — online meeting link for the pre-bid meeting
pre_bid_meeting_notesNoJSON request body field — notes for the pre-bid meeting
public_project_funding_sourceNoJSON request body field — source of funding for the public project, either 'private' or 'public'
show_location_for_nda_projectsNoJSON request body field — whether the location for the NDA project is shown
public_bid_opening_details_dateNoJSON request body field — date and time for the public bid opening in UTC (ISO 8601 format)
public_bid_opening_details_locationNoJSON request body field — location for the public bid opening
public_bid_opening_details_online_linkNoJSON request body field — online link for the public bid opening
trades_and_servicesNoJSON request body field — array of trades and services
business_classificationsNoJSON request body field — array of business classifications
Behavior4/5

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

Beyond the annotations (which indicate write but not destructive or idempotent), the description adds that only supplied fields are changed (partial update) and returns the modified object on success. It also specifies the endpoint and API, giving useful behavioral context.

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 three sentences plus a line for required parameters and API info. It is fairly concise and front-loaded, but the endpoint and API details could be considered redundant for an agent with API context.

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

Completeness4/5

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

Given the 32 parameters and no output schema, the description covers core behavior (partial update, return object) and lists required parameters. It lacks details on error handling or specific field usage, but the schema fills many gaps. Overall, it is adequate for the complexity.

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?

With 100% schema description coverage, the baseline is 3. The description lists required parameters but does not add additional semantic meaning beyond the schema's parameter descriptions. No new parameter insights are provided.

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 tool updates an existing Bid Package, specifying it modifies Bid Management records and only changes supplied fields. This provides a clear purpose, but it does not explicitly differentiate from sibling tools like create_bid_package or update_a_bid_from_a_bid_package.

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 gives context that this tool updates existing records with a partial update approach, and lists required parameters for invocation. However, it does not provide guidance on when to use this tool vs alternatives or when not to use it.

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