Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project People

list_project_people
Read-onlyIdempotent

Get a paginated list of people linked to a project, including directory and reference users. Filter by name, vendor, trade, or other criteria to locate specific records.

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 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: project_id. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/projects/{project_id}/people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
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...
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__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__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__vendor_idNoQuery string parameter — return item(s) with the specified Vendor IDs.
filters__job_titleNoQuery string parameter — returns only people who have the specified job title.
filters__country_codeNoQuery string parameter — returns only people who have the specified country code.
filters__state_codeNoQuery string parameter — returns only people who have the specified state code.
filters__trade_idNoQuery string parameter — array of Trade IDs. Returns item(s) with the specified Trade IDs.
filters__permission_template_idNoQuery string parameter — array of Permission Template IDs. Returns item(s) with the specified Permission Template IDs.
sortNoQuery string parameter — return items with the specified sort
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 behavioral context about pagination (page and per_page parameters, pagination metadata), the inclusion of reference users, and links to filtering documentation. This provides value beyond annotations, though rate limits and auth needs are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single paragraph of about 6 sentences, front-loading the core purpose. It is efficient with no filler, though it could be improved with bullet points for clarity. Still, it earns its place with specific and actionable information.

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 the complexity (17 parameters, many filters) and no output schema, the description provides a good overview but lacks details on the response structure beyond 'paginated JSON array of Directory records' and pagination metadata. It does not describe the fields in each record, which would help an agent understand what data is returned.

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 baseline is 3. The description mentions pagination parameters project_id, page, and per_page, but does not add significant meaning beyond what the schema already provides. The filtering link is helpful but not parameter-specific.

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 the tool returns a list of People associated with a Project, specifying the resource (Directory records) and the action (list). It distinguishes itself by mentioning it includes users and reference users, making the purpose unambiguous even among many sibling list tools.

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 explicit usage guidance ('Use this to enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters'), including pagination and required parameter. However, it lacks explicit when-not-to-use guidance or alternatives, which would be helpful given the number of sibling list tools.

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