Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Coordination Issue Workflow Issue

delete_coordination_issue_workflow_issue
DestructiveIdempotent

Permanently deletes a coordination issue with workflow metadata, with access limited to project admins, issue creators, assignees, and workflow members.

Instructions

Deletes a specific Coordination Issue that has associated workflow metadata. Access is controlled by the same visibility rules as other workflow issue endpoints: - Project Admins can delete all workflow issues - Issue creators can delete issues they created - Issue assignees can delete issues assigned to them - Workflow members can delete issues for workflows they are part of. Use this to permanently delete the specified Coordination Issues. This cannot be undone. Permanently removes the specified Coordination Issues. This action cannot be undone. Required parameters: company_id, project_id, id. Procore API (v2.0): Project Management > Coordination Issues. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/coordination_issues/workflow_issues/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — coordination Issue ID
Behavior4/5

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

Annotations already indicate destructiveHint=true; the description reinforces permanence ('cannot be undone') and adds access control details. No contradictions.

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?

Contains redundancy ('This cannot be undone' repeated) and unnecessary Procore API metadata. Could be more concise while retaining key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers access rules well but lacks return value information (no output schema) and does not mention idempotency or post-deletion behavior. Adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters are fully described in the schema with 100% coverage. The description only lists required parameters without adding new semantics or usage guidance beyond the schema.

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 specific Coordination Issue with workflow metadata, using strong verbs and specifying the resource. It distinguishes itself from other delete tools by targeting workflow issues.

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 access control rules (Project Admins, creators, assignees, workflow members) and states the action is permanent. Lacks explicit when-not-to-use or alternative tools, but the context is clear.

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