Skip to main content
Glama
TylerIlunga

Procore MCP Server

Bulk Delete Managed Equipment Attachment

bulk_delete_managed_equipment_attachment
DestructiveIdempotent

Permanently delete multiple managed equipment attachments in a single request. Use this to remove specified Field Productivity records; this action cannot be undone.

Instructions

Delete multiple Managed Equipment Attachments with one request. Use this to permanently delete the specified Field Productivity records. This cannot be undone. Permanently removes the specified Field Productivity records. This action cannot be undone. Required parameters: company_id, id. Procore API: Project Management > Field Productivity. Endpoint: DELETE /rest/v1.0/companies/{company_id}/managed_equipment/{id}/managed_equipment_attachments/bulk_destroy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — unique identifier of the Field Productivity resource
managed_equipment_idNoJSON request body field — iD of the Managed Equipment associated with the attachment(s)
managed_equipment_attachment_idsNoJSON request body field — iDs of all the Managed Equipment Attachment values specified for bulk destroy
Behavior4/5

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

Annotations already indicate destructive and non-readOnly. The description adds endpoint details and reinforces irreversibility. No contradiction with annotations.

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 somewhat redundant (repeats 'cannot be undone'). While it includes useful endpoint info, it could be more concise. Structure is acceptable.

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?

Without an output schema, the description omits important details like the response format, success confirmation, or error handling. For a destructive operation, this leaves gaps for an AI agent.

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 adds minimal value beyond listing required parameters. It does not elaborate on the purpose or format of each parameter beyond what the schema already provides.

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 it deletes multiple Managed Equipment Attachments with one request, using specific verbs and resources. It distinguishes from siblings like 'delete_managed_equipment_attachment' by specifying bulk operation.

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

Usage Guidelines3/5

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

The description implies usage for bulk deletion but does not explicitly contrast with alternatives like the singular delete endpoint. It mentions required parameters but lacks guidance on when not to use or when to use other tools.

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