Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Company People

list_company_people
Read-onlyIdempotent

Retrieve a paginated list of people in a Procore company directory. Filter by name, vendor, trade, or employee status to find specific directory records.

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

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__without_reference_usersNoQuery string parameter — if true, returns only people who are not reference users.
filters__reference_users_onlyNoQuery string parameter — if true, returns only people who are 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 indicate readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds behavioral context: pagination (page, per_page), response format (JSON array with metadata), and filtering capabilities. No contradictions.

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 concise but includes all necessary elements: purpose, includes, usage, pagination, required params, and API reference. It is well-structured and front-loaded, though slightly longer than necessary.

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

Completeness4/5

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

Given the tool's complexity (13 params, no output schema) and annotations, the description covers key aspects: what is returned, pagination, filtering capabilities, and required parameter. It does not detail response structure but mentions 'paginated JSON array' which is sufficient for a list endpoint.

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 descriptions for all 13 parameters. The description adds minimal additional meaning, noting company_id as required and summarizing filtering. Baseline 3 is appropriate as the description does not significantly enhance parameter understanding beyond 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 clearly states it returns a list of People associated with a Company, including directory and reference users. It distinguishes itself from other list tools by specifying the exact resource and scope.

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 for paginated overview, finding IDs, or filtering by query parameters. It references external filtering documentation but does not contrast with alternative tools for more specific scenarios.

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