Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Roles

list_project_roles
Read-onlyIdempotent

List all user-role relationships for a specified project to identify available roles and obtain role IDs for use in other Procore API calls. Read-only, paginated JSON response.

Instructions

Return a list of all relationships between Users and Roles in a specified Project. Use this to discover project roles or to look up the id of one before calling a tool that needs it. Returns a JSON array of project roles; page and per_page control pagination and the response reports how many pages remain. 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: project_id. Procore API: Core > Project. Endpoint: GET /rest/v1.0/project_roles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesQuery string parameter — unique identifier for the project.
filters__created_atNoQuery string parameter — return item(s) created within the specified ISO 8601 datetime range.
filters__add_to_project_teamNoQuery string parameter — filter results based on the `add_to_project_team` column. Accepts `true` or `false` to include or exclude items accordingly.
Behavior5/5

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

Goes beyond annotations by describing the JSON array return, pagination behavior ('response reports how many pages remain'), and specific error scenarios with HTTP status codes (401, 403, 404). The read-only statement aligns with annotations and adds human-readable confirmation.

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

Conciseness5/5

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

Front-loaded with the main purpose, then usage, return format, safety, errors, and API reference. Every sentence provides actionable information without redundancy or filler.

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

Completeness5/5

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

Despite lacking an output schema, it explains the return type (JSON array), pagination metadata, error payloads, and the required parameter. Combined with rich parameter descriptions in the schema, this gives an agent everything needed to select and invoke the tool correctly.

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?

Schema already documents all five parameters with descriptions (100% coverage), so the baseline is 3. The description adds value by explaining that page/per_page control pagination and the response reports remaining pages, and by highlighting project_id as required.

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

Purpose5/5

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

States 'Return a list of all relationships between Users and Roles in a specified Project' — a specific verb, resource, and scope. It also clarifies the lookup use case, distinguishing it from merely listing role definitions or user lists.

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?

Explicitly says 'Use this to discover project roles or to look up the id of one before calling a tool that needs it,' giving a clear invocation context. It does not name alternative tools or provide when-not-to-use guidance, so it falls short of a 5.

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