Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete BIM Model Revision Viewpoint

delete_bim_model_revision_viewpoint
DestructiveIdempotent

Permanently delete a BIM model revision viewpoint. Provide viewpoint ID and project ID to remove the associated BIM records.

Instructions

Delete BIM model revision viewpoint. Use this to permanently delete the specified BIM records. This cannot be undone. Permanently removes the specified BIM records. This action cannot be undone. Required parameters: id, project_id. Procore API: Preconstruction > BIM. Endpoint: DELETE /rest/v1.0/bim_model_revision_viewpoints/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — bim Model Revision Viewpoint ID
project_idYesQuery string parameter — unique identifier for the project.
Behavior3/5

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

Annotations already provide destructiveHint and idempotentHint. The description reinforces irreversibility ('cannot be undone') and lists required parameters, but adds minimal extra value beyond annotations. No contradiction.

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 relatively concise with a few sentences, but contains slight repetition ('This cannot be undone' appears twice). Front-loaded with purpose and usage. Minor redundancy reduces efficiency.

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 simple delete tool with two required parameters and no output schema, the description adequately covers purpose, irreversibility, required params, and API information. Lacks mention of return behavior or prerequisites, but acceptable for this complexity level.

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 coverage is 100%, and the description only lists required parameters without adding semantic details beyond what the schema already provides. Baseline of 3 is appropriate.

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 ('Delete BIM model revision viewpoint') and the resource ('BIM records'). It distinguishes from bulk alternatives by implying single-item deletion. The required parameters are mentioned.

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 indicates when to use ('permanently delete the specified BIM records') but does not explicitly mention the bulk delete sibling tool or conditions for not using. It provides clear guidance on required parameters.

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