Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Company Users

list_company_users_v1_3
Read-onlyIdempotent

List all active users for a company with pagination, filtering by date, vendor, trade, or search, and sorting options.

Instructions

Return a list of all active users associated with a company. To retrieve a list of inactive users, see List Company Inactive Users. 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/companies/{company_id}/users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). If a valid view is not provided, it will return the default view: normal.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
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.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false. The description adds that it returns a paginated JSON array and includes pagination metadata, which is helpful but not critical beyond 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 with multiple sentences that are front-loaded with purpose. Every sentence adds value, including the reference to filtering and pagination control.

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 annotations and schema richness, the description is complete: it explains the return type (JSON array), pagination, filtering, and the required parameter. No output schema exists, so the description compensates adequately.

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 coverage is 100% with good descriptions. The description mentions required parameter company_id and pagination parameters page and per_page, but adds little beyond what the schema already provides.

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 verb 'Return a list' and the resource 'all active users associated with a company', and distinguishes it from the sibling 'List Company Inactive Users' tool.

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 provides explicit use cases: 'enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters'. It does not explicitly state when not to use, but the context is clear and references filtering documentation.

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