Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Custom Field Definitions

list_custom_field_definitions_v1_0
Read-onlyIdempotent

Enumerate custom field definitions for a company with paginated results. Filter by tool name, label, scope, and sort options to find definitions.

Instructions

DEPRECATED This endpoint has been deprecated, it will be sunset at 9/1/2024. Instead, please use rest/v1.1/companies/{company_id}/custom_field_definitions. 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. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.0/custom_field_definitions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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)
viewNoQuery string parameter — the extended view provides what is shown below. The default view returns the same as the extended view but excludes the attribute custom_field_lov_entries. The with_lov_entries view is the same as ...
tool_nameNoQuery string parameter — the name of the company/project level tool that is allowed read permissions to custom field definitions.
includes_configurable_field_sets_countNoQuery string parameter — if true, response will include the number of field sets using item (custom field).
filters__with_labelNoQuery string parameter — return custom field definitions that label contains text
scope__typeNoQuery string parameter — return custom field definitions that contains fieldset type
scope__categoryNoQuery string parameter — return custom field definitions that contains category
scope__observations_category_idNoQuery string parameter — return custom field definitions that contains observations_category_id
scope__inspection_type_idNoQuery string parameter — return custom field definitions that contains inspection_type_id
scope__generic_tool_idNoQuery string parameter — return custom field definitions that contains generic_tool_id
scope__action_plan_type_idNoQuery string parameter — return custom field definitions that contains action_plan_type_id
sortNoQuery string parameter — direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter.
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds that it returns a paginated JSON array with metadata, uses pagination parameters, and requires company_id. No contradictions. Adds value 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?

Front-loaded with DEPRECATED and alternative. Each sentence has purpose, though could be slightly more concise. No wasted words.

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 no output schema, description notes paginated JSON array with metadata. Mentions pagination control and required param. Could detail available filter parameters more, but still adequate.

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 covers 100% of parameters. Description only mentions page, per_page, and company_id. Does not add meaning for other parameters beyond schema. Baseline 3 is appropriate.

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 the tool lists custom field definitions, for paginated overview, finding IDs, or filtering. It is distinct from siblings like list_custom_field_definitions_company (the replacement).

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

Usage Guidelines5/5

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

Explicitly marks as deprecated and names the replacement endpoint with URL. Tells when to use: for enumeration, paginated overview, find IDs, filter. Provides clear context for usage decisions.

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