Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Custom Field Lov Entries

list_custom_field_lov_entries
Read-onlyIdempotent

Return paginated list of custom field LOV entries for a given company and custom field definition. Filter by ID, active status, or label to narrow results.

Instructions

Return a list of all Custom Field Lov Entries associated with the Current Company and the Custom Field Definition passed by path param. The filter filters[active] is ignored when filters[id] is present. 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: company_id, custom_field_definition_id. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.0/custom_field_definitions/{custom_field_definition_id}/custom_field_lov_entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
custom_field_definition_idYesURL path parameter — unique identifier for the Custom Field Definition.
company_idYesQuery string parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__start_withNoQuery string parameter — return lov entries that label start with letters
filters__activeNoQuery string parameter — return lov entries that active status is (true or false)
filters__label_withNoQuery string parameter — return lov entries that contains the label with the text
filters__idNoQuery string parameter — return lov entries that are filtered on an array of ID's. Example: filters[id]=[1,2]
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds specific behavioral context: the interaction between filters[active] and filters[id], and that the response includes pagination metadata. This goes beyond 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?

The description is concise with clear sentences, front-loading the main purpose. It includes a critical filter behavior note and usage guidance without unnecessary fluff. Efficiently 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?

Given no output schema, the description states the return type as a paginated JSON array and mentions pagination metadata, but does not describe the fields of each entry. For a list tool, this may leave some ambiguity about the response structure. Adequate but not complete.

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 detailed descriptions for each parameter. The description restates required parameters but does not add new meaning beyond the schema. A baseline score of 3 is appropriate.

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 lists custom field LOV entries for a given company and custom field definition, and specifies the purpose: enumeration, paginated overview, finding IDs, filtering. It is specific about the resource but does not explicitly differentiate from sibling list tools, though the target is narrowly scoped.

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 provides usage guidance: 'Use this to enumerate Custom - Configurable Tools when you need a paginated overview, to find IDs, or to filter by query parameters.' It implies when to use but does not mention when not to use or suggest alternatives, leaving the agent to infer context from sibling tool names.

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