Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get All People Belonging To A Company

get_all_people_belonging_to_a_company
Read-onlyIdempotent

Retrieve all people records for a specific company using Procore's Resource Planning API. Supports pagination and filtering by name, email, or custom fields.

Instructions

Get all People belonging to a Company. Use this to fetch the full details of a specific Resource Planning records by its identifier. Returns a paginated JSON array of Resource Planning records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Resource Management > Resource Planning. Endpoint: GET /rest/v1.0/workforce-planning/v2/companies/{company_id}/people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string...
pageNoQuery string parameter — this is a **0-based index** representing the page slice of the data you want to retrieve. Each page contains up to **400 items**. ### **📌 Pageable Endpoints** People endpoints that return multiple...
first_nameNoQuery string parameter — filter results by the exact first name of the Person.
last_nameNoQuery string parameter — filter results by the exact last name of the Person.
emailNoQuery string parameter — filter results by the exact email address of the Person.
employee_numberNoQuery string parameter — filter results by the exact employee number of the Person.
custom_fields_integration_nameNoQuery string parameter — filter results by a **Custom Field's** `integration_name`. This allows searching based on custom-defined attributes in the system. Example usage: `/v2/companies/{company_id}/...?my_custom_field=nor...
created_atNoQuery string parameter — filters items based on their creation timestamp. Accepts an ISO 8601 date string.
created_beforeNoQuery string parameter — filters items created on or before the specified date (inclusive). Accepts an ISO 8601 date string.
created_afterNoQuery string parameter — filters items created on or after the specified date (inclusive). Accepts an ISO 8601 date string.
updated_atNoQuery string parameter — filters items based on their last updated timestamp. Accepts an ISO 8601 date string.
updated_beforeNoQuery string parameter — filters items updated on or before the specified date (inclusive). Accepts an ISO 8601 date string.
updated_afterNoQuery string parameter — filters items updated on or after the specified date (inclusive). Accepts an ISO 8601 date string.
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description's addition of pagination behavior, endpoint, and required parameter adds some value. However, it does not disclose rate limits, error handling, or what happens with invalid company_id.

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

Conciseness2/5

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

The description is short but contains a contradictory statement about 'all' vs 'specific', which undermines clarity. The structure is front-loaded but the mixed messaging wastes words.

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?

The description mentions pagination metadata but does not describe the response structure or field details. With no output schema, this is a significant gap. The tool has 14 parameters, but the description covers only high-level pagination.

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%, so the schema already documents all parameters thoroughly. The description only mentions required parameters and pagination control, adding minimal value beyond the schema.

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 states 'Get all People belonging to a Company' which is clear, but then contradicts itself with 'fetch the full details of a specific Resource Planning records by its identifier', creating confusion about whether the tool returns all people or a single record. It does not distinguish from siblings like 'get_all_people_belonging_to_a_group'.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of when to apply filters or when to use pagination parameters. Sibling tools exist but are not referenced for comparison.

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