Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project People

list_project_people
Read-onlyIdempotent

Return a paginated list of people linked to a Procore project, including directory and reference users. Filter by name, title, vendor, trade, or connection status to find contacts or retrieve user IDs for later use.

Instructions

Return a list of People associated with a Project. 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 project people or to look up the id of one before calling a tool that needs it. project_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of project 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: project_id. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/projects/{project_id}/people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — return items with the specified sort
viewNoQuery string parameter — specifies 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...
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.
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__country_codeNoQuery string parameter — returns only people who have the specified country code.
filters__reference_users_onlyNoQuery string parameter — if true, returns only people who are reference users.
filters__include_company_peopleNoQuery string parameter — if 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__permission_template_idNoQuery string parameter — array of Permission Template IDs. Returns item(s) with the specified Permission Template IDs.
filters__without_reference_usersNoQuery string parameter — if true, returns only people who are not reference users.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds value beyond these by detailing default project_id behavior, pagination metadata (response reports pages remaining), and common error statuses (401/403/404) with their meanings. This additional context is helpful and does not contradict 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place: purpose, scope, filtering link, use case, default behavior, return format, pagination, read-only assurance, error semantics, required parameter, and API endpoint. It is well-structured and front-loaded with the most critical information first.

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

Completeness5/5

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

For a list endpoint with 17 parameters and no output schema, this description covers all necessary context: what it returns (JSON array, pagination metadata), how to use it (discovery, ID lookup), default behaviors, error handling, and the exact API endpoint. The comprehensive parameter details are already in the schema, and the filtering link supplements it further.

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?

Schema coverage is 100%, so the baseline is 3. The description elevates this by adding meaning beyond the schema: it clarifies that project_id defaults to the value set by procore_set_config when omitted and that page/per_page control pagination with the response reporting pages remaining. These details are not explicit in the schema.

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 uses a specific verb+resource: 'Return a list of People associated with a Project' and clearly scopes the result to include both directory users and reference users. It distinguishes itself from sibling tools like list_project_users and list_company_people by explicitly defining what category of people it returns.

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 explicitly states when to use this tool: 'Use this to discover project people or to look up the id of one before calling a tool that needs it.' It also explains the default behavior of project_id via procore_set_config. However, it does not explicitly name alternative tools or state when NOT to use it, which would make it 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