Skip to main content
Glama
TylerIlunga

Procore MCP Server

Bulk Destroy Action Plan Template Receivers

bulk_destroy_action_plan_template_receivers
DestructiveIdempotent

Permanently delete multiple receivers from a Project Action Plan Template. Requires project ID, template ID, and receiver IDs. This action cannot be undone.

Instructions

Bulk Destroy Action Plan Template Receivers from a given Project Action Plan Template. Use this to permanently delete the specified Action Plans. This cannot be undone. Permanently removes the specified Action Plans. This action cannot be undone. Required parameters: project_id, plan_template_id, ids. Procore API: Project Management > Action Plans. Endpoint: DELETE /rest/v1.0/projects/{project_id}/action_plans/plan_template_receivers/bulk_destroy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
plan_template_idYesJSON request body field — iD of the Project Action Plan Template
idsYesJSON request body field — array of Receiver IDs
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description repeats 'cannot be undone' without adding new behavioral context. It lacks details on authorization, rate limits, or what happens to related data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description has redundant sentences ('This cannot be undone', 'This action cannot be undone') and includes API endpoint info. It is not concise and could be shorter without losing meaning.

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

Completeness2/5

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

For a destructive bulk operation, the description does not mention the response, confirmation of deletion, or error handling. Given no output schema, more context is needed to use the tool correctly.

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%; the description lists required parameters but adds no extra meaning beyond the schema. It does not clarify the format of the 'ids' array or provide examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Bulk Destroy Action Plan Template Receivers' but then says 'permanently delete the specified Action Plans' which is a misstatement of the resource. The verb 'destroy' is clear, but the object is inconsistently described, reducing clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Use this to permanently delete' but does not provide when-not-to-use or mention alternative tools like bulk_create_action_plan_template_receivers. No guidance on prerequisites or exclusions.

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