Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Action Plan Template Approver

delete_action_plan_template_approver
DestructiveIdempotent

Delete an action plan template approver from a Procore project. Use the list tool to get the approver ID, then call this to remove it permanently.

Instructions

Deletes an action plan template approver in the specified Procore project. Confirm the target id with the matching show or list tool before calling. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Permanently removes the action plan template approver. This cannot be undone, and a repeat call returns 404. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, id. Procore API: Project Management > Action Plans. Endpoint: DELETE /rest/v1.0/projects/{project_id}/action_plans/plan_template_approvers/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — action Plan Template Approver ID
project_idYesURL path parameter — unique identifier for the project.
Behavior5/5

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

Beyond the destructiveHint annotation, it discloses that deletion is permanent and irreversible, repeat calls return 404, and failure responses include HTTP status codes (401, 403, 404). This gives the agent essential behavioral context.

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?

The description is well-organized and front-loaded, but contains slight redundancy (e.g., the instruction to resolve the id with a list tool appears twice, and required parameters are repeated from the schema). Still, every sentence adds useful information.

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

Completeness5/5

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

Despite no output schema, the description covers purpose, prerequisites, effects, error handling, default behavior, and API endpoint. It is fully sufficient for an agent to decide when to call and what to expect.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds valuable context: project_id defaults to the configured value when omitted, and id must reference an existing parent record. This enriches the schema's basic type/description info.

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 opens with a specific verb and resource: 'Deletes an action plan template approver in the specified Procore project.' This clearly distinguishes it from sibling tools like create/show/list action plan template approvers.

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

Usage Guidelines5/5

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

It explicitly instructs to verify the target id with the matching show or list tool before calling, and advises resolving the id with the matching list tool. It also notes the project_id default behavior, providing strong guidance for correct usage.

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