Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Inactive Company People

list_inactive_company_people
Read-onlyIdempotent

Retrieve a paginated list of inactive people (directory and reference users) for a Procore company, with optional filters such as employee status, search, job title, and more. Use to enumerate records or find IDs.

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 enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Directory records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/companies/{company_id}/people/inactive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the Procore company
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.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
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.
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__connectedNoQuery string parameter — if true, returns only people who are connected users. If false, returns only people who are not connected users.
filters__state_codeNoQuery string parameter — returns only people who have the specified state code.
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__trade_idNoQuery string parameter — array of Trade IDs. Returns item(s) with the specified Trade IDs.
Behavior4/5

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

Annotations already mark the tool as read-only and idempotent. The description adds value by specifying it is a GET endpoint, returns a paginated JSON array, and links to filtering documentation, which provides behavioral context beyond the annotations.

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 adequately sized but includes redundant phrases (e.g., 'paginated' mentioned twice) and a lengthy link. Front-loading is present, but some sentences could be trimmed without losing value.

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?

Given no output schema, the description explains the return format (paginated JSON array of Directory records) and mentions pagination metadata. However, it lacks details about response fields. Annotations (e.g., openWorldHint) partially compensate, but more specificity would improve completeness for an agent.

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% with each parameter described. The description adds minimal extra meaning (e.g., mentioning page/per_page control) but does not significantly enhance understanding beyond the schema.

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 'Return a list of People associated with a Company' but does not explicitly mention that these are inactive people. The tool name and title imply the scope, but the description text itself omits 'inactive', causing potential confusion with sibling tools like 'list_company_people'.

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?

The description suggests using the tool for enumeration and pagination but provides no guidance on when to choose this over alternatives (e.g., 'list_company_people' for active users). No exclusions or scenario-based advice is given.

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