Skip to main content
Glama
TylerIlunga

Procore MCP Server

update_action_plan_item

Modify action plan items in Procore projects to update details like title, description, due dates, or status for better project tracking.

Instructions

Update Action Plan Item. [Project Management/Action Plans] PATCH /rest/v1.0/projects/{project_id}/action_plans/plan_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
idYesAction Plan Item ID
titleNoTitle of the Action Plan Item
descriptionNoDescription of the Action Plan Item
notesNoNotes for the Action Plan Item
due_atNoDue Date of the Action Plan Item
holding_typeNoAction Plan Item holding type specifies whether the current item holds all the succeeding items in the section or the plan
status_idNoStatus ID of the Action Plan Item (1 - open, 2 - in_progress, 3 - delayed, 4 - closed)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Update Action Plan Item' without explaining that this is a mutation operation, what permissions are required, whether it's idempotent, or what happens on failure. This leaves critical behavioral traits undisclosed.

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 extremely concise with just 'Update Action Plan Item' followed by a category and endpoint path. While efficient, it is under-specified rather than appropriately detailed, but it does not waste words or have structural issues.

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

Completeness2/5

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

For a mutation tool with 8 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain the update behavior, return values, error conditions, or relationship to sibling tools, leaving significant gaps in understanding how to use it effectively.

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?

The input schema has 100% description coverage, clearly documenting all 8 parameters including enums for 'holding_type' and status IDs. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage.

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

Purpose2/5

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

The description 'Update Action Plan Item' is a tautology that merely restates the tool name without adding specificity. It does not clarify what 'update' entails or distinguish this tool from sibling tools like 'bulk_update_action_plan_item' or 'create_action_plan_item', leaving the purpose vague.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It lacks any mention of prerequisites, context, or exclusions, such as when to use bulk updates or how it differs from creation or deletion tools, offering no usage instructions.

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