Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Inspection Users

list_inspection_users
Read-onlyIdempotent

Retrieves a paginated list of inspection users for a project, with filters by vendor, assignee role, distribution member, or point of contact.

Instructions

Returns a list of Inspection Users for a given project. Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Inspections. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API (v1.1): Project Management > Inspections. Endpoint: GET /rest/v1.1/projects/{project_id}/checklist/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)
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor ID.
filters__potential_assigneeNoQuery string parameter — returns item(s) with the that can be potential inspection assignees.
filters__potential_distribution_memberNoQuery string parameter — returns item(s) that can be potential distribution members.
filters__potential_point_of_contactNoQuery string parameter — returns item(s) with the that can be potential inspection points of contact.
sortNoQuery string parameter — direction of sorting param (name) is in desc order of full name
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. The description adds value by specifying pagination behavior (page, per_page, metadata) and the required project_id parameter. It also discloses the API endpoint. No contradictions 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 with 3-4 sentences, front-loading the main purpose followed by usage and details. Every sentence serves a purpose without unnecessary fluff.

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?

Given the tool has a rich schema and annotations, the description covers basic usage and pagination. However, the inconsistency between 'Inspection Users' and 'Inspections' leaves ambiguity about what exactly is returned. Also, it doesn't explain the relationship between users and inspections. This gap in clarity reduces completeness.

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%, so baseline is 3. The description adds only minimal parameter info (mentions page and per_page for pagination, project_id as required). It does not elaborate on filter parameters or sort, but the schema already provides descriptions. Added value is limited.

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

Purpose4/5

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

The description clearly states it returns a list of Inspection Users for a project, with a specific verb ('list') and resource ('Inspection Users'). However, there is a slight inconsistency when it says 'enumerate Inspections' which could cause confusion between users and inspections. Still, overall purpose is clear and distinguishes from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description suggests when to use it (paginated overview, find IDs, filter) but does not provide explicit when-not-to-use scenarios or mention alternatives among siblings. Usage is implied but not exhaustive.

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