Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Company Action Plan Template Item Assignee

delete_company_action_plan_template_item_assignee
DestructiveIdempotent

Permanently remove an assignee from a company's action plan template item. This deletion is irreversible and requires company ID and assignee ID.

Instructions

Delete Company Action Plan Template 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: company_id, id. Procore API: Project Management > Action Plans. Endpoint: DELETE /rest/v1.0/companies/{company_id}/action_plans/plan_template_item_assignees/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — unique identifier of the Action Plans resource
Behavior2/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds 'cannot be undone' which is consistent, but it incorrectly implies the tool deletes Action Plans rather than an assignee, causing confusion.

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 is repetitive, stating 'cannot be undone' twice and 'Delete Company Action Plan Template Item Assignee' in the title. It also includes API endpoint info which is not essential for invocation.

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 provided; the description does not cover success/error responses or side effects. It misrepresents the resource being deleted, leaving the agent with incomplete and inaccurate context.

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% with clear descriptions for both parameters. The description merely repeats that parameters are required, adding no extra meaning beyond the schema.

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 description states 'permanently delete the specified Action Plans,' but the tool is specifically for deleting an assignee from an action plan template item, not the entire action plan. This is misleading and contradicts the tool name and endpoint.

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 this tool vs. alternatives (e.g., delete_action_plan_item_assignee, update_company_action_plan_template_item_assignee). No prerequisites or exclusions provided.

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