Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get A Single Job Title

get_a_single_job_title
Read-onlyIdempotent

Retrieve detailed information for a specific job title within a company by providing the company and job title IDs.

Instructions

Returns details for a specific Job Title in a given company. Use this to fetch the full details of a specific Resource Planning records by its identifier. Returns a JSON object describing the requested Resource Planning records. Required parameters: company_id, job_title_id. Procore API: Resource Management > Resource Planning. Endpoint: GET /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.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already indicate read-only and idempotent. The description adds useful API context (endpoint, resource category) and confirms it returns a JSON object, enhancing transparency without contradiction.

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?

Four sentences, front-loaded with purpose, concise, with no redundant information.

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?

For a simple read tool with rich annotations, the description covers purpose, usage, required params, and API metadata. Could mention pagination but schema covers it.

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 baseline is 3. The description reiterates required parameters but adds no new meaning beyond the schema, especially for optional pagination params.

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 it returns details for a specific job title using its identifier, distinguishing it from list, create, update, and delete sibling tools.

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 says to use this tool to fetch full details by ID but does not explicitly mention when not to use it or compare to alternatives like list_all_job_titles_in_the_company.

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