Skip to main content
Glama
TylerIlunga

Procore MCP Server

List BIM Models

list_bim_models
Read-onlyIdempotent

Retrieve a paginated list of BIM Models for a project. Use filters and pagination to find specific records or IDs.

Instructions

Lists BIM Models associated with the specified Project. 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: project_id. Procore API: Preconstruction > BIM. Endpoint: GET /rest/v1.0/bim_models

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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)
viewNoQuery string parameter — the compact view contains only ids. The extended view contains the response shown below. The normal view contains 'current_revision_id' instead of an embedded object 'current_revision' The default ...
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__bim_file_idNoQuery string parameter — filter item(s) with matching BIM File ids
filters__has_revisionsNoQuery string parameter — filter item(s) with or without revisions.
filters__searchNoQuery string parameter — filter item(s) with the matching search query. The search is performed on title.
sortNoQuery string parameter — sort item(s) by an attribute. The default sort is ascending. To sort in descending order, prepend the sort value with a hyphen character '-'
Behavior4/5

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

Annotations provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by explaining pagination, return format (JSON array with metadata), and API endpoint, which complement the annotations without contradiction.

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 and well-structured: purpose, use cases, pagination details, required parameter, and API reference. Every sentence adds value with no redundancy.

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?

For a list endpoint with many parameters, the description covers core functionality, pagination, required parameters, and return type. It is adequate, though it could include a brief example or mention of filter parameters explicitly.

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%, and the description adds guidance on using page and per_page for pagination and highlights the required project_id parameter, providing additional context beyond the schema.

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 ('Lists BIM Models') and resource ('associated with the specified Project'), and it specifies use cases like enumerating records, pagination, and filtering, distinguishing it from other BIM-related 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 tells when to use the tool (enumerate, find IDs, filter) and mentions required parameters and pagination. It does not explicitly exclude alternatives, but the context of sibling tools makes it clear this is for listing only.

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