Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Bid Type

create_project_bid_type

Create a new project bid type in a Procore company. Provide the company ID and bid type name to add a new company setting.

Instructions

Create a new Project Bid Type in the specified Company. Use this to create a new Company Settings in Procore. Creates a new Company Settings and returns the created object on success (HTTP 201). Required parameters: company_id. Procore API: Company Admin > Company Settings. Endpoint: POST /rest/v1.0/companies/{company_id}/project_bid_types

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
nameNoJSON request body field — the Name of the Project Bid Type
Behavior4/5

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

Discloses creation, HTTP 201 response, endpoint, and API section beyond annotations. No contradictions.

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?

Front-loaded, but includes redundant technical details (e.g., endpoint info) that add length.

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?

Adequate for a simple create tool with no output schema; mentions required parameter and success response, but no error handling.

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 coverage is 100%; description adds no extra meaning and omits the name parameter mention.

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 'Create a new Project Bid Type' (specific verb+resource) and distinguishes from siblings like delete/update/list_project_bid_types.

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?

Includes 'Use this to create a new Company Settings', but no explicit when-to-use vs alternatives or when-not-to-use guidance.

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