Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Action Plan Item Assignee

delete_action_plan_item_assignee
DestructiveIdempotent

Permanently delete a specified action plan item assignee using project ID and assignee ID. This action cannot be undone.

Instructions

Delete Action Plan Item Assignee. 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, id. Procore API: Project Management > Action Plans. Endpoint: DELETE /rest/v1.0/projects/{project_id}/action_plans/plan_item_assignees/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — action Plan Item Assignee ID
Behavior3/5

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

Annotations already indicate destructiveHint=true; the description adds 'cannot be undone' and 'Permanently removes', which are consistent but redundant. It does not reveal cascading effects or permissions needed.

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 is verbose with repeated phrases ('cannot be undone' appears twice, 'Permanently removes' appears twice). Could be more concise.

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?

No output schema, so description should explain what happens on success/failure or any preconditions. It does not; plus the error about 'Action Plans' reduces completeness for this specific tool.

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%, so the description listing required parameters adds no new meaning. Parameter descriptions in schema are clear. Baseline 3.

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

Purpose2/5

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

The tool name and title indicate it deletes an action plan item assignee, but the description repeatedly says 'delete the specified Action Plans', which is a different entity. This inconsistency misleads the agent about the tool's purpose.

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?

No guidance on when to use or not use this tool versus alternatives (e.g., recycle, batch delete). The description only states 'Use this to permanently delete' without context.

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