Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Task Item

create_task_item

Create a task item on a Procore project by providing project_id and optional fields such as title, status, due date, and assignees. Returns the new task item with its ID.

Instructions

Creates a task item on a given project. Pass the record's fields as top-level arguments — they are nested under "task_item" in the request payload for you. Creates the task item and returns it with its new id (HTTP 201); calling it again creates another record. 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. Procore API: Core > Tasks. Endpoint: POST /rest/v1.0/task_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoQuery string parameter — serialization view for the created task item in the response. Defaults to **`extended`** when omitted.
titleNoJSON request body field — the title for this Tasks operation
numberNoJSON request body field — the number for this Tasks operation
statusNoJSON request body field — the status for this Tasks operation
privateNoJSON request body field — privacy flag
due_dateNoJSON request body field — due date in YYYY-MM-DD format
form_idsNoJSON request body field — forms to attach to the response
image_idsNoJSON request body field — images to attach to the response
project_idYesQuery string parameter — unique identifier for the project.
upload_idsNoJSON request body field — uploads to attach to the response
assigned_idNoJSON request body field — unique identifier of the assigned
attachmentsNoJSON request body field — task Item attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files.
descriptionNoJSON request body field — the description for this Tasks operation
assignee_idsNoJSON request body field — array of assignee identifiers
file_version_idsNoJSON request body field — file Versions to attach to the response
prostore_file_idsNoJSON request body field — array of prostore file identifiers
drawing_revision_idsNoJSON request body field — drawing Revisions to attach to the response
task_item_category_idNoJSON request body field — the task item category to associate with the task item.
distribution_member_idsNoJSON request body field — distribution Member IDs
document_management_document_revision_idsNoJSON request body field — pDM document to attach to the response
Behavior4/5

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

The description discloses the HTTP 201 response with new id, non-idempotency, and common error statuses (401/403/404). These behaviors go beyond the annotations, which only set idempotentHint=false and readOnlyHint=false. No contradiction exists; the description reinforces the annotation semantics.

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?

Every sentence earns its place: purpose, param passing, response/non-idempotency, error handling, required parameter, and API reference. The description is front-loaded with the primary action and avoids redundant or vague wording.

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?

Given the 20-parameter schema and no output schema, the description covers purpose, parameter handling, required params, response status, error behavior, and endpoint. It doesn't enumerate all return fields, but it does indicate the new id is returned, which is sufficient for a create operation.

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?

The schema already covers all 20 parameters with descriptions (100% coverage), so the baseline is 3. The description adds critical context: body fields should be passed as top-level arguments and are nested under 'task_item' in the payload. This clarifies the exact invocation contract, which is not evident from the schema alone.

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 a specific verb-resource-scope statement: 'Creates a task item on a given project.' This clearly distinguishes it from sibling tools like list_task_items, show_task_item, or update_task_item by focusing on the creation operation. The endpoint and API reference further tie it to the exact resource.

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?

It provides clear context: creation on a given project, required project_id, and non-idempotent behavior ('calling it again creates another record'). It also explains how to pass parameters (top-level arguments) and typical error conditions. However, it does not explicitly contrast with alternatives like create_task, so it stops short of full when/when-not 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