Skip to main content
Glama
TylerIlunga

Procore MCP Server

List BIM Property File Properties

list_bim_property_file_properties
Read-onlyIdempotent

Retrieve properties from a BIM Property File using its ID and project ID, with pagination and filters for object ID, category, name, value, query, curated list, or unit of measurement.

Instructions

Lists properties from a specific BIM Property File. A BIM Property File is a resource that represents a 3d-model database. For models published to the Models tool, the property file id can be found in BIM Model Revision object_definition -> id. For models uploaded and extracted with Procore Documents, the property file id can be found in [BIM File Extraction](https://developers.procore... Use this to enumerate BIM records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of BIM records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: id, project_id. Procore API: Preconstruction > BIM. Endpoint: GET /rest/v1.0/bim_property_files/{id}/properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — bIM Property File ID.
project_idYesQuery string parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__object_idNoQuery string parameter — filter item(s) with matching object_id.
filters__categoryNoQuery string parameter — filter item(s) with matching category.
filters__nameNoQuery string parameter — filter item(s) with matching name.
filters__valueNoQuery string parameter — filter item(s) with matching value.
filters__queryNoQuery string parameter — filter item(s) containing query. Searchable fields include Property Category, Name, and Value
filters__curated_listNoQuery string parameter — filter item(s) to return a curated list of properties
filters__has_uomNoQuery string parameter — filter item(s) to return properties with/without unit of measurement (uom).
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. The description adds that the tool returns a paginated JSON array of BIM records and mentions pagination metadata. It also names the API endpoint and required parameters. Beyond pagination details, it does not disclose additional behavioral traits like rate limits, authorization needs, or error handling, which would add more value.

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 fairly comprehensive yet reasonably concise. It front-loads the main action and then provides context about BIM Property Files, usage guidance, and technical details. The structure is logical, but the truncated URL and slight repetition (mentioning pagination twice) could be tightened. Overall, it is well-organized and efficiently informative.

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 the tool's complexity (11 parameters, no output schema), the description provides key contextual information: what a BIM Property File is, how to find its ID, the return type (paginated JSON array), and pagination controls. It also lists the API endpoint and required parameters. While it could elaborate more on filter behavior or error responses, it covers the essential aspects adequately for a list endpoint.

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 for all 11 parameters, so the baseline is 3. The description emphasizes required parameters and pagination (page, per_page) but adds little meaning beyond what the schema already provides. For example, it does not explain the filter parameters beyond what is in the schema, so it does not significantly enhance understanding.

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 that the tool lists properties from a specific BIM Property File, and provides context on how to find the property file ID in other Procore resources. It also notes that the tool is for enumerating BIM records with paginated overview and filtering, which establishes its purpose. However, it does not explicitly differentiate from potential sibling tools that might list properties from other sources, such as model revisions.

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 explains when to use the tool: to enumerate BIM records for a paginated overview, find IDs, or filter by query parameters. It also identifies required parameters and provides pagination control instructions. However, it does not specify when not to use the tool or suggest alternative tools for related tasks, leaving the agent to infer context without explicit exclusions.

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