Skip to main content
Glama
TylerIlunga

Procore MCP Server

List BIM Levels

list_bim_levels
Read-onlyIdempotent

List BIM levels for a project with pagination and filtering options. Retrieve IDs or detailed records using query parameters.

Instructions

Lists BIM Levels 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_levels

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 'bim_file_id', 'location_id', and 'created_by_id' instead of embedded objects. The ...
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__location_idNoQuery string parameter — location ID. Returns item(s) with the specified Location ID or a range of Location IDs.
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 already provide readOnlyHint, destructiveHint, etc. Description adds value by stating it returns a paginated JSON array with pagination metadata and the exact endpoint path. No contradictions 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.

Conciseness4/5

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

Description is five sentences, well-structured, and front-loaded with purpose. Could be slightly more concise but is efficient and clear.

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?

No output schema, but description states the return type (paginated JSON array of BIM records) and mentions pagination metadata. For a simple list tool, this is sufficiently complete. Also includes the API endpoint for further context.

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?

Schema has 100% coverage with descriptions for all parameters. The description briefly mentions required parameter project_id and pagination parameters page/per_page, but adds minimal new meaning beyond what the schema already provides.

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?

Clearly states the tool lists BIM Levels for a project. Verb 'Lists' plus 'BIM Levels' and 'associated with the specified Project' makes the purpose unambiguous. Distinguishes from sibling list tools like list_bim_files by focusing on BIM Levels.

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?

Provides explicit usage scenarios: 'enumerate BIM records when you need a paginated overview, to find IDs, or to filter by query parameters.' Does not mention when not to use it or alternative tools, but the guidance is clear enough for an agent to decide.

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