Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get A Groups Projects

get_a_groups_projects
Read-onlyIdempotent

Retrieve the projects assigned to a company group. Supports pagination and filtering by name, project number, custom fields, and timestamps.

Instructions

Get the projects for a given company ID and group ID. 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. Procore API: Resource Management > Resource Planning. Endpoint: GET /rest/v1.0/workforce-planning/v2/companies/{company_id}/groups/{group_id}/projects

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...
nameNoQuery string parameter — filters items by their exact name. The query performs an exact match. Example usage: `/v2/companies/{company_id}/...?name=Bridge+Restoration`
project_numberNoQuery string parameter — filters items by their exact project number. The query performs an exact match. Example usage: `/v2/companies/{company_id}/...?project_number=BR-2024`
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)
Behavior4/5

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

Annotations already indicate read-only, idempotent behavior. The description adds value by specifying pagination (page and per_page), return format (paginated JSON array), and providing API endpoint details. 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.

Conciseness3/5

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

The description is a single dense paragraph covering multiple aspects but includes redundant phrasing (e.g., 'fetch the full details of a specific Resource Planning records'). It could be more concise and structured.

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

Completeness3/5

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

Given 13 parameters and no output schema, the description provides pagination details and API source. However, it does not explain the relationship between 'Resource Planning records' and projects, nor potential errors or limits. The high schema coverage compensates partially.

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 baseline is 3. The description does not add significant meaning beyond the schema, merely reiterating required parameters and pagination. No new parameter insights.

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?

The description clearly states the tool gets projects for a company and group, with specific verb and resource. It distinguishes from siblings by focusing on projects of a group, but does not explicitly differentiate from similar tools like 'get_all_company_groups'.

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?

The description explains when to use the tool (fetch projects for a given company and group) and mentions pagination parameters. However, it lacks explicit guidance on when not to use it or alternatives, such as other grouping tools.

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