Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Lookahead Task

update_lookahead_task

Update a Lookahead Task in the project schedule by modifying specified fields like name, dates, resources, or assignees. Returns the updated task object.

Instructions

Update a Lookahead Task for the project schedule. Use this to update an existing Schedule (Legacy) records (only the supplied fields are changed). Updates the specified Schedule (Legacy) records and returns the modified object on success. Required parameters: project_id, id, lookahead_id, parent_id, name. Procore API: Project Management > Schedule (Legacy). Endpoint: PATCH /rest/v1.0/projects/{project_id}/schedule/lookahead_tasks/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Schedule (Legacy) resource
lookahead_idYesJSON request body field — iD of the associated Lookahead
parent_idYesJSON request body field — iD of the parent Lookahead Task
nameYesJSON request body field — the name of the Task
start_dateNoJSON request body field — task start date, in project time zone
end_dateNoJSON request body field — task end date, in project time zone
resource_idsNoJSON request body field — iD of Resource(s) to assign to this Lookahead Task
commentNoJSON request body field — additional comments
segmentsNoJSON request body field — the segments for this Schedule (Legacy) operation
assignee_idsNoJSON request body field — iD of Contact(s) to assign to this Lookahead Task
vendor_idsNoJSON request body field — iD of Company(s) to assign to this Lookahead Task
Behavior4/5

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

Annotations declare non-read-only, non-destructive, non-idempotent. The description adds that it only changes supplied fields and returns the modified object, providing transparency beyond annotations. No contradiction.

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 concise with two sentences plus API details. It front-loads the purpose and adds necessary context without fluff.

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?

With high schema coverage and no output schema, the description sufficiently explains the update operation, partial update behavior, and return value. Includes API endpoint for reference.

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 has 100% coverage with descriptions for all 12 parameters. The description redundantly lists required parameters but adds no new semantic meaning beyond the schema. Baseline of 3 is appropriate.

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 'Update a Lookahead Task for the project schedule' with specific verb and resource. It distinguishes from other update tools by naming the target object and specifying it is for Schedule (Legacy) records.

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 says 'Use this to update an existing Schedule (Legacy) records' but does not provide explicit when-not-to-use or alternative tools. It only mentions that only supplied fields are changed, which is implicit usage 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