Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Types For A Company User

list_project_types_for_a_company_user
Read-onlyIdempotent

Retrieves paginated project types for a user by company and user IDs. Use to filter or enumerate directory records.

Instructions

This endpoint returns the list of Project Types for the specified User. 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, user_id. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/companies/{company_id}/users/{user_id}/project_assignments/filter_options/project_types

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
user_idYesURL path parameter — unique identifier of the user
scopeNoQuery string parameter — the scope to use when getting the filter options for project assignments. The user scope returns only filter options for projects that the user is currently assigned to. The company scope returns a...
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already indicate read-only and idempotent. Description adds pagination behavior and response format (paginated JSON array with metadata), which is useful context.

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?

Four sentences, front-loaded with purpose, no fluff. Every sentence adds value.

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?

Even without output schema, description covers return type and pagination metadata. Mentions API endpoint. Complete enough for a simple list tool.

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 description adds minimal value beyond restating required parameters and pagination usage. Adequate but not exceptional.

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 it returns a list of Project Types for a specified user, with specific verb and resource. It distinguishes from siblings by being user-scoped and for project types.

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 clear usage scenarios (paginated overview, find IDs, filter) and mentions required parameters. Lacks explicit when-not-to-use or alternatives, but sufficient for a simple list.

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