Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Program

delete_program
DestructiveIdempotent

Delete a program permanently from Procore. Prevent errors by verifying the program ID with the list tool first; requires company_id and id.

Instructions

Delete the specified Program. Confirm the target id with the matching show or list tool before calling. company_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 program. 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: company_id, id. Procore API: Company Admin > Company Settings. Endpoint: DELETE /rest/v1.0/companies/{company_id}/programs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Company Settings resource
company_idYesURL path parameter — unique identifier for the company.
Behavior5/5

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

Beyond annotations, it discloses that the operation 'Permanently removes the program,' 'cannot be undone,' and that 'a repeat call returns 404.' It details error payloads with common HTTP statuses (401/403/404), which annotations do not provide. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence adds value: purpose, prerequisites, consequences, error behavior, required params, API context. It is structured logically and not padded.

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?

For a destructive delete tool with no output schema, it covers prerequisites, irreversibility, default parameter behavior, and failure modes. This is sufficient for an agent to safely invoke with correct expectations.

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

Parameters4/5

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

Schema covers both params, so baseline is 3. Description adds value by noting company_id defaults to procore_set_config and that id must be resolved via the list tool. The phrase 'existing parent record' is slightly ambiguous, but overall it supplements the schema.

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 'Delete the specified Program,' a specific verb+resource statement. It reinforces the target with the endpoint 'DELETE /rest/v1.0/companies/{company_id}/programs/{id}' and clearly distinguishes this tool from sibling delete tools by naming the Program resource.

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 'Confirm the target id with the matching show or list tool before calling' and 'resolve it with the matching list tool first,' naming prerequisite tools. It also explains the company_id default from procore_set_config, giving clear context on when and how to invoke.

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