Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Job Title

update_a_job_title

Update a job title for a company by providing its ID, new name, and type (hourly or salaried) to modify Resource Planning records.

Instructions

Updates a Job Title given a company ID and job title ID. Use this to perform the update a action on Resource Planning records. Creates a new Resource Planning records and returns the created object on success (HTTP 201). Required parameters: company_id, job_title_id, name, type. Procore API: Resource Management > Resource Planning. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/job-titles/{job_title_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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...
job_title_idYesURL path parameter — unique identifier for the Job Title.
nameYesJSON request body field — name of the Job Title.
globally_accessibleNoJSON request body field — controls whether the Job Title is globally available to all current and future Groups.
colorNoJSON request body field — hexadecimal color code for the Job Title. Helps with categorization and visual distinction.
typeYesJSON request body field — specifies the Job Title type. - `hourly` - Hourly wage-based job title. - `salaried` - Fixed salary job title.
hourly_rateNoJSON request body field — hourly wage rate for the Job Title. Required if type is `hourly`.
Behavior2/5

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

The description reveals the HTTP 201 response and endpoint details, but the core action is ambiguous due to the update/create contradiction. Annotations offer no additional insight, and the description fails to clarify the tool's true behavior.

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?

The description is moderately concise at four sentences, but includes unnecessary repetition and contradictory statements. It could be more tightly focused without the conflicting create/update language.

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

Completeness2/5

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

With 7 parameters and no output schema, the description should cover conditional requirements (e.g., hourly_rate required if type is hourly) and optional parameters. It only mentions required params, leaving gaps in understanding.

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%, so parameters are already well-documented. The description lists required parameters and the endpoint template, but adds no semantic value beyond what the schema provides. Baseline score of 3 is appropriate.

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

Purpose2/5

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

The description starts by saying 'Updates a Job Title' but later contradicts by stating 'Creates a new Resource Planning records'. This inconsistency with the tool name and sibling 'create_a_job_title' creates confusion about the actual operation.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives like 'create_a_job_title'. The description is misleading, claiming an update operation but describing a create operation, leaving the agent without clear decision criteria.

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