Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Create Task

create_task

Create a new schedule (legacy) task in Procore for a specified project using project ID and task object.

Instructions

Create a new Task associated with the specified Project. 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, task. Procore API: Project Management > Schedule (Legacy). Endpoint: POST /rest/v1.0/tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesJSON request body field — iD of the project this task belongs to.
taskYesJSON request body field — task object.

Tool Definition Quality

A4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds that it returns the created object on success with HTTP 201, which is useful context. No contradictions.

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, front-loaded with the main purpose, and includes necessary usage and API info 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?

The description covers the action, required parameters, and return value. The nested 'task' object is not elaborated, but the schema provides structure. Adequate for a simple create tool.

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% with clear descriptions for both parameters. The tool description adds no additional parameter details beyond what the schema provides. Baseline 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 it creates a Task associated with a Project and specifically for Schedule (Legacy) records in Procore. This differentiates it from other task creation tools like create_project_task_company.

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 create a new Schedule (Legacy) records in Procore' but does not provide explicit guidance on when not to use it or compare with sibling tools like create_project_task_company.

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