Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A Job Title

create_a_job_title

Create a job title in Procore for a specified company. Set name, group availability, and global access to add a new role to workforce planning.

Instructions

Creates a new Job Title in the specified company. company_id defaults to the value set by procore_set_config when omitted. Creates the job title 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: company_id, name, group_ids, globally_accessible. Procore API: Resource Management > Resource Planning. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/job-titles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesJSON request body field — the name of the Job Title.
typeNoJSON request body field — indicates whether the Job Title is salaried or hourly.
colorNoJSON request body field — hexadecimal color code for the Job Title. Helps with categorization and visual distinction.
group_idsYesJSON request body field — array of UUIDs for which Groups this Job Title should be available to. If `globally_accessible` is set to `true`, this value can be an empty array.
company_idYesURL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string...
hourly_rateNoJSON request body field — the rate value that will be factored into cost calculations for any person who has this job title applied and doesn't already have a standalone hourly wage value. This is also handy for costing man...
globally_accessibleYesJSON request body field — controls whether the Job Title should be globally available to all current and future Groups.
Behavior5/5

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

Annotations provide readOnlyHint=false, idempotentHint=false, but the description adds significant context: company_id defaults to procore_set_config, returns HTTP 201 with the new id, explicitly states non-idempotency, and enumerates common error statuses (401, 403, 404) with causes. This goes well beyond annotation cues.

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 five sentences covering purpose, default, return, non-idempotency, errors, and required params. Every sentence adds actionable information with no fluff.

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

Completeness5/5

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

Given no output schema, the description covers expected return (new id, HTTP 201), error handling, and side-effect behavior. It includes the API endpoint and area. For a create tool, this is sufficiently 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?

Schema description coverage is 100%, providing baseline 3. The description adds value by explaining that company_id defaults to the procore_set_config value and by listing required parameters, though it doesn't elaborate on other params beyond schema.

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 Job Title in the specified company', providing a specific verb ('Creates') and resource ('Job Title') with scope. It also names the endpoint, which clearly differentiates from sibling tools like update/delete/get job titles.

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 implies usage for creating job titles but does not explicitly state when to use it vs alternatives like update_a_job_title. It notes 'calling it again creates another record' as a behavioral warning rather than a usage guideline, so guidance is only implied, not explicit.

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