Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Lookahead Task

create_lookahead_task

Create a new Lookahead Task in Procore's Schedule (Legacy) using project, lookahead, parent IDs, and task name.

Instructions

Create new Lookahead Task for the project schedule. Use this to create a new Schedule (Legacy) records in Procore. Creates a new Schedule (Legacy) records and returns the created object on success (HTTP 201). Required parameters: project_id, lookahead_id, parent_id, name. Procore API: Project Management > Schedule (Legacy). Endpoint: POST /rest/v1.0/projects/{project_id}/schedule/lookahead_tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
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
Behavior3/5

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

Annotations already indicate the tool is not read-only or destructive. The description adds that it returns the created object on success and mentions HTTP 201, but does not disclose failure modes, side effects, or rate limits.

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 verbose with redundant phrasing ('Create new... Use this to create... Creates a new...'). It could be more concise while retaining key info like the required parameters and endpoint.

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

Completeness3/5

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

Given the lack of output schema, the description should clarify the return structure. It only says 'returns the created object' without details. Also, the relationship between Lookahead Task and Schedule (Legacy) is ambiguous.

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 only restates required fields without adding meaning beyond the schema. No explanation of the 'lookahead_id' or 'parent_id' relationships is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (create) and resource (Lookahead Task). It distinguishes from sibling tools like update_lookahead_task and delete_lookahead_task by using 'Create'. However, it conflates 'Lookahead Task' with 'Schedule (Legacy) records', which may cause confusion.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., create_lookahead). The description repeats the purpose but does not specify prerequisites, context, or when not to use it.

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