Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Task Item

update_task_item

Update a task item's attributes in a Procore project. Modify fields like title, status, or due date to keep task information accurate.

Instructions

Update a task item's attributes. Use this to update an existing Tasks (only the supplied fields are changed). Updates the specified Tasks and returns the modified object on success. Required parameters: project_id, id. Procore API: Core > Tasks. Endpoint: PATCH /rest/v1.0/task_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Tasks resource
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 already indicate a mutation (readOnlyHint=false). The description adds that it returns the modified object and only updates supplied fields, which is helpful. However, it does not disclose side effects, authorization requirements, or error behavior beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise with three sentences that front-load the main action. It includes useful API context (endpoint and Procore API reference). A slight redundancy exists ('Update a task item's attributes' and 'Updates the specified Tasks'), but overall it is efficient.

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?

The description covers the core action (update), required parameters, and return value. However, with 20 parameters, it lacks context about default values, preconditions, error scenarios, or rate limits. The return value is mentioned, but no output schema exists. It is adequate but not thorough.

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 description coverage is 100%, so the baseline is 3. The description only reiterates required parameters (project_id, id) and the concept of partial update, which is already implied by the schema. It adds no additional meaning beyond the schema.

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 task item's attributes' and specifies it updates existing Tasks, returning the modified object. It distinguishes itself from siblings by focusing on updates of task items, and the verb 'update' paired with the resource 'task item' is specific.

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?

The description explicitly says 'Use this to update an existing Tasks' and notes that only supplied fields are changed, guiding appropriate usage. It also mentions required parameters (project_id, id). However, it does not mention alternatives or exclusions (e.g., when not to use) among many sibling 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