Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Company People

list_company_people
Read-onlyIdempotent

List people associated with a Procore company, including directory and reference users. Filter by name, email, trade, or job title to find specific individuals and their IDs.

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 discover company people or to look up the id of one before calling a tool that needs it. company_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of company 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: company_id. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/companies/{company_id}/people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
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.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
company_idYesURL path parameter — unique identifier for the Procore company
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__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.
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds useful behavioral context beyond these: 'Returns a JSON array of company people; page and per_page control pagination and the response reports how many pages remain' and '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.' It also explicitly states 'Read-only — it changes nothing in Procore,' which reinforces the annotations without contradicting them. This is strong supplementary information, though not exhaustive (no rate limits or deeper auth scopes).

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 lengthy but well-structured: it opens with the core function, then covers filtering, use case, default behavior, return format, safety, error handling, required parameters, and API reference. Every sentence carries actionable information. It is not as tight as the two-sentence ideal, but it avoids filler and maintains high informational density.

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?

Given the tool has 13 parameters and no output schema, the description is remarkably complete. It specifies the return type (JSON array), pagination semantics, error scenarios (401/403/404), default company_id behavior, required parameters, and links to filtering documentation. It also names the Procore API section and endpoint. This equips an agent to call the tool correctly without needing external lookups.

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?

The schema provides 100% parameter descriptions, so the baseline is 3. The description adds meaningful extra semantics: company_id 'defaults to the value set by procore_set_config when omitted,' and it explains pagination behavior ('page and per_page control pagination and the response reports how many pages remain') beyond what the schema offers. It also points to filtering documentation. This raises the score above baseline.

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 opens with a specific verb+resource statement: 'Return a list of People associated with a Company.' It further clarifies scope ('Includes users in the directory and reference users') and gives an explicit use case ('Use this to discover company people or to look up the id of one before calling a tool that needs it'). This distinguishes it from sibling tools like list_project_people or list_company_users.

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 clearly states when to use the tool: 'Use this to discover company people or to look up the id of one before calling a tool that needs it.' It also notes that company_id defaults to the value set by procore_set_config when omitted, which is practical context. However, it does not explicitly exclude alternatives (e.g., list_project_people for project-scoped people), so it falls short of a full when-to-use/when-not-to-use contrast.

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