Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Webhooks Hook

delete_webhooks_hook
DestructiveIdempotent

Permanently delete a specific webhook hook by providing its ID, company ID, and project ID. This action cannot be undone.

Instructions

Triggers must be deleted within a company and/or project scope. Use this to permanently delete the specified Webhooks. This cannot be undone. Permanently removes the specified Webhooks. This action cannot be undone. Required parameters: id, company_id, project_id. Procore API: Platform - Developer Tools > Webhooks. Endpoint: DELETE /rest/v1.0/webhooks/hooks/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Webhooks resource
company_idYesQuery string parameter — unique identifier for the company. You must supply either a company_id or project_id.
project_idYesQuery string parameter — unique identifier for the project. You must supply either a company_id or project_id.
Behavior4/5

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

Annotations already indicate destructiveHint=true, and the description reinforces irreversibility ('cannot be undone'), adding clarity on scope constraints beyond annotations.

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 moderately concise with front-loaded key information (scope, action, permanence). The inclusion of API endpoint is slightly extraneous but not excessive.

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

Completeness4/5

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

For a deletion tool with no output schema, the description adequately covers purpose, scope, required parameters, and irreversibility, making it complete enough for correct invocation.

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?

Input schema covers 100% of parameters with descriptions. The description only lists required parameters without adding new semantic meaning, so baseline 3 applies.

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 the tool deletes webhooks permanently, using specific verb ('delete') and resource ('Webhooks'), and differentiates from siblings like 'delete_company_webhooks_hook' by mentioning company and project scope.

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 mentions scope constraints ('within a company and/or project scope') but does not explicitly state when to use this tool versus alternatives like 'delete_company_webhooks_hook' or 'delete_project_webhooks_hook'. No exclusions are 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