Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Meeting

delete_meeting_v1_0
DestructiveIdempotent

Permanently delete a specific meeting by providing its ID and project ID. This action cannot be undone.

Instructions

Delete a specified meeting from the system. Use this to permanently delete the specified Meetings. This cannot be undone. Permanently removes the specified Meetings. This action cannot be undone. Required parameters: id, project_id. Procore API: Project Management > Meetings. Endpoint: DELETE /rest/v1.0/meetings/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Meetings resource
project_idYesQuery string parameter — unique identifier for the project.
Behavior4/5

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

Annotations already mark destructiveHint=true and idempotentHint=true. The description reinforces that deletion is permanent ('cannot be undone'), adding context beyond the 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 relatively short and front-loaded, but contains some repetition ('This cannot be undone' appears twice), which could be tightened.

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 simplicity of a delete operation and annotations covering destructiveness, the description sufficiently covers behavior and required inputs. No major gaps.

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?

Input schema covers both parameters with descriptions. The description merely restates that id and project_id are required, adding no new semantic value beyond the schema.

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 it deletes a meeting and emphasizes permanence. However, it does not differentiate from other delete tools among many siblings, which slightly reduces clarity.

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 tells when to use it (to delete a meeting) and states required parameters, but lacks explicit guidance on when not to use it or mention of alternative tools for similar operations.

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