Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Inactive Company People

list_inactive_company_people
Read-onlyIdempotent

Get inactive people for a Procore company. Filter by search, job title, vendor, or trade to identify inactive contacts and retrieve their IDs for further use.

Instructions

Return a list of People associated with a Company. Includes Users in the Directory and Reference Users. See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to discover inactive company people or to look up the id of one before calling a tool that needs it. company_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of inactive company people; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. 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. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/companies/{company_id}/people/inactive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). If a valid view is not provided, it will default to normal.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
company_idYesURL path parameter — unique identifier for the Procore company
filters__searchNoQuery string parameter — returns People where the search string matches the Person's name (first, last, or full), email address, mobile phone, business phone, fax number, or job title.
filters__trade_idNoQuery string parameter — array of Trade IDs. Returns item(s) with the specified Trade IDs.
filters__connectedNoQuery string parameter — if true, returns only people who are connected users. If false, returns only people who are not connected users.
filters__job_titleNoQuery string parameter — returns only people who have the specified job title.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor IDs.
filters__state_codeNoQuery string parameter — returns only people who have the specified state code.
filters__is_employeeNoQuery string parameter — if true, returns item(s) where `is_employee` value is true.
filters__reference_users_onlyNoQuery string parameter — if true, returns only people who are reference users.
filters__without_reference_usersNoQuery string parameter — if true, returns only people who are not reference users.
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds concrete behavior: the response is a JSON array, pagination is controlled by page and per_page, and the response reports how many pages remain. It also details common error statuses (401, 403, 404) and default company_id behavior, which are not captured in annotations.

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 compact and every sentence serves a purpose: purpose, filtering link, usage, default behavior, return type/pagination, safety, error handling, required params, and API reference. It is front-loaded with the primary action and then covers necessary operational details without waste.

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?

With no output schema, the description still conveys the return type and key behavior. It covers pagination, error handling, required parameter, and the API endpoint. It doesn't enumerate the exact fields of the returned person objects, but the filtering link and parameter schema fill most gaps. Given the tool's moderate complexity, this is a high level of completeness.

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?

The input schema already documents all 13 parameters at 100% coverage, so the baseline is 3. The description adds value by clarifying that company_id defaults to procore_set_config and that page/per_page control pagination with a pages-remaining count, which is not in the schema. This extra context justifies a 4.

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 a specific verb+resource: 'Return a list of People associated with a Company.' It clearly specifies the scope (inactive company people, including Users in the Directory and Reference Users), which distinguishes it from sibling list tools like list_company_people or list_inactive_project_people.

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

Usage Guidelines4/5

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

The description provides a direct usage scenario: 'Use this to discover inactive company people or to look up the id of one before calling a tool that needs it.' It also explains the company_id default behavior via procore_set_config. However, it does not explicitly name alternative tools or state when not to use it, so it falls slightly short of a 5.

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