Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List User Permissions

list_user_permissions_project
Read-onlyIdempotent

Retrieve the full set of privileges for the current user on a specific Procore project. Use this to get detailed permission fields when you need the complete permission data.

Instructions

Returns the list of privileges/permissions for the current user. Use this when you already know which user permission you want and need its full field set. company_id and project_id default to the values set by procore_set_config when omitted. Returns a single JSON object describing the user permission. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: company_id, project_id. Procore API (v2.0): Core > Assets. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/assets/permissions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
Accept-LanguageNoJSON request body field — locale for localized response messages (for example: en, fr-FR, pseudo)

Tool Definition Quality

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, but the description adds concrete error behavior (401/403/404), defaulting behavior, and return type. 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.

Conciseness4/5

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

Description is information-dense but not bloated; covers usage, defaults, errors, and endpoint in an organized way. Slightly overlong with repeated 'Required parameters' and API details, but generally well-structured.

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?

Covers return type, error handling, and defaulting, but leaves ambiguity between 'list' and 'single JSON object' and doesn't clarify what 'user permission' refers to. No output schema, so return description is minimal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of params, so baseline 3. Description adds value by explaining that company_id and project_id default to procore_set_config values when omitted, which is not in schema. Thus 4.

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 the list of privileges/permissions for the current user, with a specific endpoint and scope. However, it does not differentiate from sibling list_user_permissions_company and mixes 'list' with 'single JSON object', creating slight ambiguity.

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?

Provides explicit usage context: 'Use this when you already know which user permission you want and need its full field set.' Also mentions defaulting of company_id/project_id from procore_set_config. No explicit alternatives or when-not-to-use, so 4.

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