Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_company_people

Retrieve and filter company personnel data from Procore, including employees, vendors, and contacts, with options to search by name, role, or status.

Instructions

List Company People. [Core/Directory] GET /rest/v1.0/companies/{company_id}/people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesID of the company
viewNoSpecifies 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.
pageNoPage
per_pageNoElements per page
filters__is_employeeNoIf true, returns item(s) where `is_employee` value is true.
filters__without_reference_usersNoIf true, returns only people who are not reference users.
filters__reference_users_onlyNoIf true, returns only people who are reference users.
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__state_codeNoReturns only people who have the specified state code.
filters__job_titleNoReturns only people who have the specified job title.
filters__vendor_idNoReturn item(s) with the specified Vendor IDs.
filters__trade_idNoArray of Trade IDs. Returns item(s) with the specified Trade IDs.
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. It implies a read-only list operation via 'GET', but doesn't disclose pagination behavior, rate limits, authentication needs, or what 'List' entails (e.g., returns all people or a subset). The API path hints at a REST endpoint, but behavioral details are missing, making it inadequate for a tool with 13 parameters.

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, efficient sentence with the API path. It's front-loaded with the core purpose and wastes no words. However, it could be more structured (e.g., separating purpose from technical details).

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 tool's complexity (13 parameters, no annotations, no output schema), the description is insufficient. It lacks behavioral context, usage guidelines, and output details. While the schema covers parameters, the description doesn't compensate for missing annotations or output schema, leaving the agent under-informed.

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 the schema fully documents all 13 parameters. The description adds no parameter-specific information beyond implying 'company_id' is required via the API path. This meets the baseline of 3, as the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List Company People. [Core/Directory] GET /rest/v1.0/companies/{company_id}/people' restates the tool name with minimal elaboration. It specifies the resource ('Company People') and HTTP method but lacks a clear, specific verb beyond 'List' and doesn't differentiate from sibling tools. This is a tautology with minor API context, scoring above 1 due to the added API path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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, context, or exclusions. With many sibling tools present, this absence is a significant gap, leaving the agent without direction.

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