Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Task Item

create_task_item

Create a new task item in a Procore project. Provide project ID and task details to add a task with title, description, due date, and more.

Instructions

Creates a task item on a given project. Use this to create a new Tasks in Procore. Creates a new Tasks and returns the created object on success (HTTP 201). Required parameters: project_id. Procore API: Core > Tasks. Endpoint: POST /rest/v1.0/task_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
titleNoJSON request body field — the title for this Tasks operation
numberNoJSON request body field — the number for this Tasks operation
descriptionNoJSON request body field — the description for this Tasks operation
due_dateNoJSON request body field — due date in YYYY-MM-DD format
statusNoJSON request body field — the status for this Tasks operation
task_item_category_idNoJSON request body field — the task item category to associate with the task item.
privateNoJSON request body field — privacy flag
assigned_idNoJSON request body field — unique identifier of the assigned
assignee_idsNoJSON request body field — array of assignee identifiers
distribution_member_idsNoJSON request body field — distribution Member IDs
prostore_file_idsNoJSON request body field — array of prostore file identifiers
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.
drawing_revision_idsNoJSON request body field — drawing Revisions to attach to the response
file_version_idsNoJSON request body field — file Versions to attach to the response
form_idsNoJSON request body field — forms to attach to the response
image_idsNoJSON request body field — images to attach to the response
upload_idsNoJSON request body field — uploads to attach to the response
document_management_document_revision_idsNoJSON request body field — pDM document to attach to the response
Behavior3/5

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

Annotations declare readOnlyHint=false, which aligns with the creation intent. The description adds that it returns the created object on success (HTTP 201), which is useful but not extensive. No contradictions and no additional behavioral details such as side effects or required permissions.

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 repetitive ('Creates a task item' and 'Creates a new Tasks' appear twice) and could be more streamlined. At 6 sentences, it is moderately concise but not optimally structured for quick scanning.

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 tool's complexity (19 parameters, no output schema), the description provides the endpoint and a basic success response but does not explain the response structure, prerequisites, or project context. It is minimally sufficient for an agent to use the tool but lacks completeness.

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 input schema already describes all 19 parameters in detail. The description only highlights 'project_id' as required, which is already in the schema. No additional meaning or context is added beyond what the schema provides, so a 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 the verb 'Creates' and the resource 'task item on a given project', with explicit mention of the Procore API endpoint and success response (HTTP 201). It is specific enough to distinguish the tool from generic 'create' operations, though sibling tools like 'create_task' exist but are not differentiated.

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?

The description does not provide guidance on when to use this tool versus alternatives (e.g., 'create_task', 'create_project_task_company'). It only states what the tool does and the required parameter, but lacks context for tool selection among similar create tools.

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