Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Custom Fields User Options

list_custom_fields_user_options
Read-onlyIdempotent

Retrieves a paginated list of user options for a custom field tool in a project, allowing you to find user IDs and filter by search query.

Instructions

Returns login informations that have access to the specified tool. Use this to enumerate Custom - Configurable Tools when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Custom - Configurable Tools. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id, tool_name. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.0/projects/{project_id}/custom_fields/{tool_name}/user_options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
tool_nameYesURL path parameter — tool name identifier
filters__searchNoQuery string parameter — filters results by the search query
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior2/5

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

Annotations (readOnlyHint=true, etc.) indicate a safe read operation. However, the description introduces ambiguity by mentioning 'login informations' without clarifying sensitivity or access requirements. It does not add value beyond annotations and may mislead.

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 somewhat lengthy with redundant details (e.g., Procore API endpoint, required parameters). It could be more concise by focusing on core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema provided. The description only states 'paginated JSON array' without specifying fields. Given the tool's complexity (5 parameters) and lack of output schema, more detail is needed for the agent to use the response correctly.

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 clear parameter descriptions. The description mentions pagination parameters and required fields but adds no extra meaning. Baseline score of 3 is appropriate.

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

Purpose2/5

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

The description states 'Returns login informations that have access to the specified tool' but then refers to 'Custom - Configurable Tools', which is contradictory. The tool name suggests listing user options for custom fields, but the description's resource is unclear. This vagueness hinders purpose clarity.

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

Usage Guidelines2/5

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

The description suggests using it for enumeration, paginated overview, finding IDs, or filtering, but lacks guidance on when not to use or alternatives. Given the purpose confusion, an agent would struggle to decide when to invoke this tool over siblings.

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