Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Custom Field Metadata

list_custom_field_metadata
Read-onlyIdempotent

Retrieve a paginated list of custom field metadata for a company or project. Use to find IDs, filter by field set type or ID, and control pagination.

Instructions

Return a list of all Custom Field Metadata associated with the Current 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. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.0/custom_field_metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idNoQuery string parameter — unique identifier for the company. You must supply either a company_id or project_id.
project_idNoQuery string parameter — unique identifier for the project. You must supply either a company_id or project_id.
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 attributes company_id, host_type, source_type, source_id, label, data_type. T...
filters__field_set_type__NoQuery string parameter — return a list of all Custom Field Metadata associated with the Current Company and source_type provided.
filters__field_set_id__NoQuery string parameter — return a list of all Custom Field Metadata associated with the Current Company and source_id provided.
filters__custom_field_definitions_idNoQuery string parameter — return a list of all Custom Field Metadata associated with the Current Company and custom_field_definition_id provided.
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds context about pagination, response format (JSON array), and association with Current Company. It does not contradict 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 and well-structured, presenting purpose, usage, and API details in a logical order. It could be slightly more concise by removing the Procore API line, but it remains effective.

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, the description sufficiently covers the return format (paginated JSON array) and pagination controls. It mentions filtering by query parameters and the association with Current Company. It is complete for a list endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining that page and per_page control pagination and that the response includes pagination metadata, which is not in the schema. This provides useful behavioral context.

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 returns a list of Custom Field Metadata associated with the Current Company, and specifies use cases like enumeration, finding IDs, and filtering. It is a specific verb-resource combination, distinguishing it from sibling list tools.

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?

The description explicitly states when to use the tool (enumeration, paginated overview, finding IDs, filtering) and provides the API endpoint. However, it does not mention when not to use it or compare with alternatives among 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