Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_project_people

Retrieve people associated with a Procore project, including employees, vendors, and contacts, with filtering options for roles, permissions, and search.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for 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 the full burden of behavioral disclosure. It states 'List Project People' and includes a GET endpoint, implying a read-only operation, but doesn't explicitly confirm safety (e.g., non-destructive), discuss permissions, rate limits, pagination behavior, or error handling. For a tool with 17 parameters and no annotation coverage, this leaves significant gaps in understanding its operational traits.

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 brief and front-loaded with the core purpose ('List Project People'), followed by technical context in brackets. It wastes no words, though it could be more structured (e.g., separating purpose from endpoint). The single sentence is efficient, but the inclusion of the endpoint adds slight clutter without clear value for an AI agent.

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 the return format (e.g., list of people objects), pagination handling (implied by 'page' and 'per_page' but not described), or error scenarios. For a list operation with many filters, more context on behavior and output is needed to complement the rich input schema.

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%, with detailed descriptions for all 17 parameters (e.g., 'project_id' as 'Unique identifier for the project', 'view' with enum values and permission notes). The description adds no parameter-specific information beyond the schema, but since the schema is comprehensive, the baseline score of 3 is appropriate as the description doesn't detract from the schema's clarity.

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 'List Project People' restates the tool name and adds minimal context with '[Core/Directory] GET /rest/v1.0/projects/{project_id}/people', indicating it's a GET request to list people in a project. However, it lacks specificity about what 'people' means (e.g., team members, contacts) and doesn't distinguish it from sibling tools like 'list_company_people' or 'get_all_people_belonging_to_a_company', making it vague in differentiation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., project access), exclusions, or compare it to sibling tools like 'list_company_people' or 'get_all_people_belonging_to_a_group'. Without such context, an agent must infer usage solely from the name and schema.

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