Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete Lookahead

delete_lookahead
DestructiveIdempotent

Permanently delete a single lookahead from a Procore project schedule by providing project_id and id. The action is irreversible, so confirm the correct record first.

Instructions

Deletes a single Lookahead. 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 lookahead. 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 (v1.1): Project Management > Schedule (Legacy). Endpoint: DELETE /rest/v1.1/projects/{project_id}/schedule/lookaheads/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Schedule (Legacy) resource
project_idYesURL path parameter — unique identifier for the project.

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

Beyond annotations (destructiveHint, idempotentHint), it discloses permanence ('This cannot be undone'), repeat-call behavior (404), and maps common error codes (401, 403, 404) to causes. This enriches the agent's understanding of failure modes and side effects.

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?

Clear lead sentence and organized information, but slightly redundant: the instruction to resolve id appears twice ('Confirm the target id with the matching show or list tool' and 'resolve it with the matching list tool first'). Also repeats required params from schema.

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?

Covers purpose, prerequisites, permanence, error behavior, parameter defaults, and API endpoint. Minor gap: no explicit statement about successful response body, but acceptable for a delete with no output schema.

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 already covers both params with descriptions, so baseline is 3. The description adds that project_id defaults to procore_set_config when omitted and that id must be resolved via list tool first, providing practical guidance beyond 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?

Description opens with 'Deletes a single Lookahead,' clearly stating the action and resource. This distinguishes it from sibling tools like create_lookahead, show_lookahead, and delete_lookahead_task.

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

Usage Guidelines4/5

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

Explicitly instructs to 'Confirm the target id with the matching show or list tool before calling' and to 'resolve it with the matching list tool first.' It also explains project_id default behavior via procore_set_config, giving clear context for when to call. It does not name specific alternative tools but provides sufficient prerequisite guidance.

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