Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Custom Field Definitions

list_custom_field_definitions_company
Read-onlyIdempotent

Retrieve a paginated list of custom field definitions for a company to enumerate configurable tools, locate IDs, or apply filters. Required: company_id.

Instructions

Return a list of Custom Field Definitions for a given company. 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 (v1.1): Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.1/companies/{company_id}/custom_field_definitions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — items per page, default: 100, max: 100
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
filters__idNoQuery string parameter — return custom field definitions that are filtered on an array of ID's. Example: filters[id]=[1,2]
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 indicate read-only, idempotent, and open-world behavior. The description adds value by specifying the response format (paginated JSON array), pagination parameters, and endpoint details. 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.

Conciseness5/5

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

The description is concise with 5 sentences, each serving a purpose: purpose, usage, response format, parameters, and API reference. It is well-structured and front-loaded with key information, with no wasted words.

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?

The description mentions paginated JSON array and includes metadata, but does not detail the structure of each returned item (Custom Field Definition). Given the absence of an output schema, more detail on return fields would improve completeness.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds minor usage context for page and per_page but does not introduce new semantic meaning beyond what the schema provides.

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 a list of Custom Field Definitions for a given company, using specific verbs and resource identification. It mentions use cases like paginated overview and filtering, but does not explicitly differentiate from sibling list tools. The title aligns well, making the purpose clear.

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 context on when to use the tool ('to enumerate Custom - Configurable Tools when you need a paginated overview'), but lacks guidance on when not to use it or alternatives. No mention of alternative tools like list_custom_field_definitions_configurable_field_sets.

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