Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Users

list_project_users
Read-onlyIdempotent

Retrieve active users for a project with pagination and filtering. Use this to get directory records, find IDs, or filter by parameters.

Instructions

Returns a list of active users associated with a project. See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Directory records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/projects/{project_id}/users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). Users without read permissions to Directory are limited to the compact view. Otherwise, the defa...
filters__created_atNoQuery string parameter — return item(s) created within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-...
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
filters__permission_templateNoQuery string parameter — permission Template ID. Returns item(s) assiociated with the specified Permission Template ID.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor IDs.
filters__origin_idNoQuery string parameter — origin ID. Returns item(s) with the specified Origin ID.
filters__trade_id__NoQuery string parameter — returns users whose vendor record is associated with the specified trade id(s).
filters__searchNoQuery string parameter — returns users where the search string matches the user's first name, last name, email address, keywords, job title, or company name
filters__employeeNoQuery string parameter — returns users whose is_employee attribute matches the parameter.
filters__idNoQuery string parameter — returns users whose id attribute matches the parameter.
sortNoQuery string parameter — returns items with the specified sort.
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by detailing that the output is a paginated JSON array with metadata, mentions pagination control (page, per_page), and specifies the required project_id. This context enhances transparency without contradicting annotations.

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?

The description is a single paragraph, front-loaded with the main purpose. It includes useful details (filtering, pagination, API endpoint) without being overly verbose. Could be slightly more concise by removing the API endpoint line, but overall well-structured.

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 the tool has 14 parameters and no output schema, the description covers the core functionality, filtering, pagination, and required parameters. It references external filtering documentation, which is a plus. Lacks details on error handling or specific filter parameters, but is sufficient for a list endpoint. Annotations provide readOnly and idempotent hints, completing the picture.

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 mentions required parameter project_id and refers to filtering and pagination parameters, but does not add significant meaning beyond what the schema already provides. It includes a link to filtering documentation, which is helpful but not essential.

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?

The description clearly states 'Returns a list of active users associated with a project' with a specific verb and resource. It also provides use cases (enumerate Directory records, find IDs, filter by query parameters), distinguishing it from other list tools by focusing on project users and pagination.

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?

The description gives explicit context on when to use this tool ('when you need a paginated overview, to find IDs, or to filter') and references filtering documentation. However, it does not explicitly mention when not to use it or provide alternatives, such as other user listing 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