Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Submittal

delete_submittal
DestructiveIdempotent

Delete a specific submittal permanently by providing project ID and submittal ID. This action cannot be undone.

Instructions

Delete the specified Submittal. Use this to permanently delete the specified Submittals. This cannot be undone. Permanently removes the specified Submittals. This action cannot be undone. Required parameters: project_id, id. Procore API (v1.1): Project Management > Submittals. Endpoint: DELETE /rest/v1.1/projects/{project_id}/submittals/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Submittals resource
Behavior4/5

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

Annotations provide destructiveHint=true, and the description reinforces permanence and irreversibility. Additional context includes required parameters and API endpoint details, going 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.

Conciseness3/5

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

The description contains redundancy (e.g., 'cannot be undone' repeated, 'permanently delete' repeated). Could be more concise.

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 delete tool, the description covers the action, persistence, required parameters, and API details. Lacks info on cascading effects but is largely complete.

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 lists required parameters and their role as URL path parameters, but adds little beyond the schema definition.

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 tool deletes a submittal, emphasizes permanence, and distinguishes from numerous sibling delete tools by focusing on submittals specifically.

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 (to permanently delete submittals) but provides no guidance on when not to use or alternatives. Basic usage context is present.

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