Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Company Users

list_company_users_v1_3_2
Read-onlyIdempotent

Retrieve a paginated list of users in a company directory. Filter by status, creation date, or search terms to find specific directory records.

Instructions

Return a list of all Users associated with a Company. 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: company_id. Procore API (v1.3): Core > Directory. Endpoint: GET /rest/v1.3/users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesQuery string parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__activeNoQuery string parameter — if true, returns item(s) with a status of 'active'.
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__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 — return users where the search string matches the user's first name, last name, email address, keywords, job title, or company name
sortNoQuery string parameter — return 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, destructiveHint=false, idempotentHint=true. The description adds value by explaining that the tool returns a paginated JSON array with pagination metadata and mentions filtering capabilities. No contradiction with annotations.

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?

The description is concise, consisting of 5 sentences that efficiently convey the tool's purpose, usage, filtering reference, pagination, required parameter, and endpoint info. No redundancy or filler.

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 11 parameters and no output schema, the description covers essential aspects: pagination control, filtering capabilities (with link), output format (paginated JSON array), and required parameter. It could mention rate limits or response structure details, but overall it is reasonably complete.

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?

The input schema has 100% coverage with detailed descriptions for all 11 parameters. The description only briefly mentions page and per_page for pagination and filtering, adding minimal extra meaning beyond the schema. Baseline score 3 is appropriate.

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 the tool returns a list of all users associated with a company, specifying the verb 'Return' and resource 'Users'. It distinguishes the tool's purpose (enumerate Directory records, paginated overview, find IDs, filter) from sibling tools like list_company_inactive_users.

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 explains when to use the tool (enumerate records, paginated overview, find IDs, filter by query parameters) and mentions the required parameter (company_id). It does not explicitly state when not to use or provide alternatives, but the usage context is clear.

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