Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_inactive_project_people

Retrieve inactive personnel from a Procore project directory to manage team access and update project records.

Instructions

List Inactive Project People. [Core/Directory] GET /rest/v1.0/projects/{project_id}/people/inactive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesID of the project
viewNoSpecifies which view of the resource to return (which attributes should be present in the response). Users without read permissions to Directory are limited to the normal and extended views. If a v...
pageNoPage
per_pageNoElements per page
filters__is_employeeNoIf true, returns item(s) where `is_employee` value is true.
filters__reference_users_onlyNoIf true, returns only people who are reference users.
filters__without_reference_usersNoIf true, returns only people who are not reference users.
filters__include_company_peopleNoIf true, returns people in the Company not just the Project. This option only works if the user has permission to create people in the project directory or permission to read from the company direc...
filters__searchNoReturns 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__connectedNoIf true, returns only people who are connected users. If false, returns only people who are not connected users.
filters__vendor_idNoReturn item(s) with the specified Vendor IDs.
filters__job_titleNoReturns only people who have the specified job title.
filters__country_codeNoReturns only people who have the specified country code.
filters__state_codeNoReturns only people who have the specified state code.
filters__trade_idNoArray of Trade IDs. Returns item(s) with the specified Trade IDs.
filters__permission_template_idNoArray of Permission Template IDs. Returns item(s) with the specified Permission Template IDs.
sortNoReturn items with the specified sort
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'List Inactive Project People' which implies a read-only operation, but doesn't disclose any behavioral traits: no mention of pagination behavior (though parameters exist), no rate limits, no authentication requirements, no details about what 'inactive' means in this context, and no information about return format or structure. The description is minimally functional but lacks critical behavioral context.

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 extremely concise ('List Inactive Project People. [Core/Directory] GET /rest/v1.0/projects/{project_id}/people/inactive') but this brevity comes at the cost of clarity. While it's front-loaded with the core function, the API path adds technical noise without explanatory value for an AI agent. The single sentence approach is efficient but under-specified rather than optimally concise.

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?

Given the complexity (17 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain what constitutes 'inactive' people, doesn't describe the return structure, doesn't mention pagination behavior (though parameters exist), and provides no context about permissions or data scope. For a tool with rich filtering capabilities and no output schema, the description should do much more to help the agent understand what to expect.

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 description coverage is 100%, so the schema already documents all 17 parameters thoroughly. The description adds no parameter semantics beyond what's in the schema - it doesn't explain relationships between filters, doesn't clarify the meaning of 'inactive' in relation to parameters, and provides no usage examples. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to heavily.

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 'List Inactive Project People' is a tautology that restates the tool name without adding meaningful context. It lacks a specific verb and resource definition beyond the obvious, and doesn't distinguish this tool from sibling list tools like 'list_project_people' or 'list_inactive_company_people'. The API path included adds technical detail but doesn't clarify the purpose for an AI agent.

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?

The description provides zero guidance on when to use this tool versus alternatives. With many sibling tools for listing people (e.g., 'list_project_people', 'list_inactive_company_people', 'list_company_people'), there's no indication of when 'inactive' status matters or what context would call for this specific filter. The agent receives no usage context.

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