Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Group Assignments

get_group_assignments
Read-onlyIdempotent

Retrieve Resource Planning assignments for a specified group within a date range. Returns paginated details for workforce planning.

Instructions

Returns the Resource Planning Assignment data for the given company and group. 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, group_id, dayRange, start_day. Procore API: Resource Management > Resource Planning. Endpoint: GET /rest/v1.0/workforce-planning/v2/companies/{company_id}/groups/{group_id}/assignments

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...
group_idYesURL path parameter — unique identifier for the group
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...
dayRangeYesQuery string parameter — a value specifying how many days forward you would like to get assignments for from the specified startDay. Assignments whose start_day falls within the given range will be returned in the response...
start_dayYesQuery string parameter — the starting day to filter assignments by.
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 declare readOnlyHint=true and idempotentHint=true, so the description adds little beyond confirming pagination and required parameters. It does not disclose additional behavioral traits beyond what annotations imply.

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?

Description is relatively short and front-loaded. It includes some extra info like the API endpoint path which may be redundant for an agent, but overall it is efficient.

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 no output schema, the description adequately explains the response is a paginated JSON array with metadata, and lists required parameters. It is complete enough for a read-only paginated list tool.

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 baseline is 3. Description adds context on pagination (use page and per_page) and required parameters, but does not significantly improve understanding beyond what the schema already provides.

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

Purpose4/5

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

Description clearly states it returns Resource Planning Assignment data for a given company and group, using specific verbs and resources. However, it mentions 'by its identifier' which is slightly ambiguous as it returns multiple records.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description provides context on when to use (fetch full details of specific records) but does not explicitly differentiate from sibling tools like get_company_assignments or get_person_assignments, nor state when not to use.

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