Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Create Line Item Type

create_line_item_type

Create a new Line Item Type for Procore Commitments, such as Labor, by providing the company ID and line item type object.

Instructions

Create a new Line Item Type (e.g. L2 for Labor). Use this to create a new Commitments in Procore. Creates a new Commitments and returns the created object on success (HTTP 201). Required parameters: company_id, line_item_type. Procore API: Construction Financials > Commitments. Endpoint: POST /rest/v1.0/line_item_types

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesJSON request body field — unique identifier for the Procore company
line_item_typeYesJSON request body field — line Item Type object

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

Description misleadingly mentions 'create Commitments' (likely an error) and does not clarify idempotency or side effects beyond HTTP 201. Annotations provide basic safety info but description adds confusion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is moderately concise but repeats 'create a new Commitments' twice and includes redundant info. Not optimally structured.

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?

Provides endpoint and API area, but lacks explanation of line_item_type object structure or relationship to Commitments. Adequate for a simple tool but not thorough.

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 covers both parameters fully (100% coverage). Description merely repeats them without adding extra meaning, meeting baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it creates a Line Item Type but then confusingly says 'create a new Commitments,' conflating two different entities. This vagueness reduces clarity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like sync_line_item_types or update_line_item_type. Lacks exclusions or context about typical use cases.

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