Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Context By ID

delete_context_by_id
DestructiveIdempotent

Permanently delete a Document Markup context and all associated layers, groups, and markups using company, project, and context IDs. This action cannot be undone.

Instructions

Delete a context and all its associated layers, groups, and markups using context ID. Pass skip_resource_deletion=true when the caller has already deleted external resources. Use this to permanently delete the specified Document Markup records. This cannot be undone. Permanently removes the specified Document Markup records. This action cannot be undone. Required parameters: company_id, project_id, context_id. Procore API: Project Management > Document Markup. Endpoint: DELETE /rest/v1.0/companies/{company_id}/projects/{project_id}/contexts/{context_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the Procore company
project_idYesURL path parameter — unique identifier for the Procore project
context_idYesURL path parameter — unique identifier of the context
skip_resource_deletionNoQuery string parameter — skip_resource_deletion
Behavior5/5

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

Annotations already indicate destructive=true, but the description adds important context: it deletes associated layers, groups, and markups, and stresses irreversibility. No contradiction 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?

Reasonably concise, though repeated warnings about irreversibility are redundant. Front-loaded with essential action and critical parameters.

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?

Covers the deletion scope, irreversibility, required parameters, and API details. Lacks output schema but annotations sufficiently warn of destructiveness.

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?

Input schema has 100% description coverage, so baseline is 3. Description adds value by listing required parameters and explaining the 'skip_resource_deletion' parameter's purpose.

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 it deletes a context and all associated layers, groups, and markups by ID, distinguishing from the sibling tool 'delete_context_by_query_parameters' which uses query parameters.

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 guidance for the 'skip_resource_deletion' parameter and mentions this tool is for permanent deletion of Document Markup records. However, it does not explicitly exclude other scenarios or list alternatives.

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