Skip to main content
Glama
TylerIlunga

Procore MCP Server

List BIM Model Revision Properties

list_bim_model_revision_properties
Read-onlyIdempotent

Retrieve properties of a BIM Model Revision with pagination and filtering. Use to enumerate BIM records and find specific properties by ID, category, name, or value.

Instructions

Lists properties for a specific BIM Model Revision. 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_model_revisions/{id}/properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — bIM Model Revision 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).
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral details such as the return format (paginated JSON array), pagination control via page and per_page, and inclusion of pagination metadata. This enriches the agent's understanding 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 reasonably concise at about three sentences, starting with the core purpose and then providing usage guidance, return type, and pagination details. While it includes extraneous Procore API info, it remains clear and on-topic without excessive verbosity.

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 the tool has 11 parameters (many filter options) and no output schema, the description adequately covers pagination and filter usage. However, it does not elaborate on the meaning of 'BIM records' or the specific filter fields beyond their presence, leaving some context gaps for a complex tool with many parameters.

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% coverage with descriptions for all 11 parameters. The description highlights required parameters (id, project_id) and mentions pagination and filtering capabilities, but does not significantly add meaning beyond what is already in the schema. It confirms the purpose of filters but lacks detailed semantics.

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 action (list), resource (properties for a specific BIM Model Revision), and provides specific use cases such as enumerating BIM records for paginated overview, finding IDs, or filtering by query parameters. It distinguishes from sibling tools by explicitly naming the resource and parameters.

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 advises when to use this tool (for paginated overview, finding IDs, filtering) and specifies required parameters. However, it does not explicitly mention when not to use it or provide direct alternatives among the sibling tools, relying on the specific resource name for differentiation.

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