Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Bid Package

create_bid_package

Create a new bid package in a Procore project with details like due date, messages, and title. Simplifies setting up bidding for construction projects.

Instructions

Creates a new bid package in the specified Procore project. Pass the record's fields as top-level arguments — they are nested under "bid_package" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted. Creates the bid package and returns it with its new id (HTTP 201); calling it again creates another record. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, bid_due_date, bid_email_message, bid_web_message, title. Procore API: Preconstruction > Bid Management. Endpoint: POST /rest/v1.0/projects/{project_id}/bid_packages

Input Schema

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

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

The description discloses that parameters are accepted as top-level args and nested under 'bid_package' in the request payload, which is beyond the schema. It also details failure modes with specific HTTP status codes (401, 403, 404) and states the return behavior (new id, HTTP 201). This adds significant context beyond the 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 structured and front-loaded: action first, then argument handling, defaults, response, errors, and required params. Every sentence serves a purpose, and no filler is present. The length is justified given the tool's complexity.

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 31 parameters and no output schema, the description covers the essential invocation, response, and error information. It doesn't explain the full response body but provides the new id and HTTP status, which is adequate for a create operation. A brief note on validation or relationships could push it to 5, but it's quite complete.

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?

The schema already covers all 31 parameters (100% coverage), so the baseline is 3. The description adds value by explicitly listing the required parameters and explaining the project_id default behavior. It also clarifies the payload nesting, which helps avoid invocation errors.

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 opens with 'Creates a new bid package in the specified Procore project,' which clearly states the verb and resource. It distinguishes from sibling tools like update_bid_package and list_bid_packages_project by using 'creates' and mentioning the POST endpoint. The scope is specific and unambiguous.

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?

The description provides clear context by stating it creates a new bid package, and the note that 'calling it again creates another record' signals non-idempotency. It mentions project_id defaults to procore_set_config, aiding tool selection. However, it does not explicitly name alternatives like update_bid_package or list_bid_packages_project, so it falls short of a 5.

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