Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Assignments For A Company User

list_project_assignments_for_a_company_user
Read-onlyIdempotent

Retrieve current and potential project assignments for a user, including permission templates and roles. Filter by project stage, type, status, or assignment status for targeted results.

Instructions

This endpoint returns the current and potential Project assignments for the specified User. This includes Project information, as well as the Permission Template and Roles assigned to a given user when they are assigned on a Project. Use this to enumerate Project records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Project records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, user_id. Procore API: Core > Project. Endpoint: GET /rest/v1.0/companies/{company_id}/users/{user_id}/project_assignments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
user_idYesURL path parameter — unique identifier of the user
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__nameNoQuery string parameter — filter item(s) with matching name.
filters__by_stageNoQuery string parameter — return item(s) with the specified project stage ID(s).
filters__by_typeNoQuery string parameter — return item(s) with the specified project type ID(s).
filters__by_programNoQuery string parameter — return item(s) with the specified project program ID(s).
filters__by_regionNoQuery string parameter — return item(s) with the specified project region ID(s).
filters__by_statusNoQuery string parameter — return item(s) with the specified status value. Must be one of Active, Inactive, or All.
filters__project_rolesNoQuery string parameter — return item(s) with the Project Role ID(s).
filters__project_permission_templatesNoQuery string parameter — return item(s) with the Project Permissions Template ID(s).
filters__assignment_statusNoQuery string parameter — filters projects to those matching the given assignment status.
sortNoQuery string parameter — sort the results by the specified field.
directionNoQuery string parameter — sort direction. Default is ascending, nulls first.
Behavior3/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, so the description adds value by specifying pagination behavior and included data (permission templates, roles). However, it does not disclose authorization needs, rate limits, or potential side effects beyond what annotations provide.

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

Conciseness3/5

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

The description is well-structured and front-loaded, but includes redundant details like 'Procore API: Core > Project. Endpoint: GET /rest/...' and repeated required parameters, which could be trimmed for conciseness.

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 16 parameters, no output schema, and moderate complexity, the description adequately covers return format (paginated JSON with project, permission template, roles), pagination control, and filtering capability. Missing aspects like error handling or edge cases, but overall sufficient for an agent.

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?

Input schema has 100% description coverage, so the baseline is 3. The description only mentions required parameters (company_id, user_id) and pagination params, adding no additional meaning beyond the schema for the other 12 parameters.

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 the tool returns current and potential project assignments for a specific user, including project info, permission templates, and roles. However, it does not explicitly differentiate from sibling list tools like list_company_assignments or list_person_assignments, which limits clarity for tool selection.

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 advises using the tool for paginated overview, finding IDs, or filtering, but lacks explicit when-not-to-use guidance or mention of alternative tools. It does note required parameters, which is helpful but not sufficient for complete usage direction.

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