Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Bid Packages

list_bid_packages_company
Read-onlyIdempotent

Retrieve a paginated list of bid packages for a company using company ID. Filter results by sort parameters like bid package name or due date.

Instructions

Return a list of Bid Packages for a Company. Use this to enumerate Bid Management records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Bid Management records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Preconstruction > Bid Management. Endpoint: GET /rest/v1.0/companies/{company_id}/bid_packages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
sortNoQuery string parameter — direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds that it returns a paginated JSON array with metadata and specifies the required company_id parameter. This adds some behavioral context beyond annotations but is not extensive.

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 with clear structure: purpose, use cases, then details (pagination, required param, endpoint). No unnecessary information; every sentence adds value.

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?

No output schema exists; description compensates by noting a paginated JSON array with metadata. It covers required parameter, pagination, and endpoint. Sibling tool for project-level exists but is not referenced. Overall complete for a list tool with robust annotations.

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?

Input schema has 100% coverage with descriptions for all 4 parameters. Description mentions using page and per_page for pagination but does not add significant new semantics beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states the tool returns a list of Bid Packages for a Company and specifies use cases (enumerate, find IDs, filter). The title 'List Bid Packages' is generic, and the description does not explicitly differentiate from the sibling tool 'list_bid_packages_project', but mentions 'Company' and the endpoint path implies company scope.

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?

Description provides use cases (enumerate, find IDs, filter) and mentions pagination controls. However, it does not specify when not to use this tool or mention alternatives like the project-level sibling tool.

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