Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Groups

get_groups
Read-onlyIdempotent

Retrieve all accessible groups with pagination and filtering, providing company_id and project_id for full group details from the Procore Document Markup API.

Instructions

Returns all accessible groups with pagination and filtering. Use this when you already know which group you want and need its full field set. company_id and project_id default to the values set by procore_set_config when omitted. Returns a single JSON object describing the group. 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, project_id. Procore API (v2.0): Project Management > Document Markup. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/domains/groups

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for pagination (1-based)
per_pageNoQuery string parameter — number of items per page (max 5000 for ids_only)
company_idYesURL path parameter — unique identifier of the company
project_idYesURL path parameter — unique identifier of the project
filters__idNoQuery string parameter — jSON array of group IDs to filter by
filters__context_idNoQuery string parameter — context ID to filter groups by
filters__updated_atNoQuery string parameter — filter by updated_at range in ISO format (start...end)
filters__created_beforeNoQuery string parameter — filter groups created before this ISO date-time
filters__context_type_idNoQuery string parameter — context type ID to filter by
filters__subcontext_type_idNoQuery string parameter — sub-context type ID to filter by
Behavior4/5

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

Beyond the annotations, it details defaulting behavior for company_id/project_id from procore_set_config, error payloads with common HTTP status codes, and reiterates read-only semantics. This adds useful behavioral context beyond the annotation flags.

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 compact but contains a contradictory statement about returning 'all accessible groups' versus a 'single JSON object,' which undermines structure. It also includes API metadata that is somewhat extraneous for tool selection.

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?

It covers pagination, filtering, defaults, errors, and endpoint, but the ambiguous return shape (list vs object) is a critical gap given there is no output schema. Also, the relationship to sibling group-related tools is not clarified.

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 already covers all 10 parameters with descriptions (100% coverage). The description enriches the required parameters by noting they default to procore_set_config values when omitted, which is not in 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 opens with 'Returns all accessible groups with pagination and filtering' but later says 'Returns a single JSON object describing the group', which is contradictory about the return shape. The verb and resource are present, but the ambiguity and lack of distinction from sibling tools like get_all_company_groups or get_a_single_group reduce clarity.

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?

It provides an explicit use case: 'Use this when you already know which group you want and need its full field set.' This gives clear context but does not name alternatives or exclusions, so no when-not-to-use guidance.

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