Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Action Plan

update_action_plan
Idempotent

Update an existing action plan in a Procore project by sending only the fields you want to change; the modified plan is returned.

Instructions

Updates an existing action plan in the specified Procore project. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "plan" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified action plan on success. 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, id. Procore API: Project Management > Action Plans. Endpoint: PATCH /rest/v1.0/projects/{project_id}/action_plans/plans/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Action Plans resource
titleNoJSON request body field — title of the Action Plan
privateNoJSON request body field — privacy flag of the Action Plan
asset_idsNoJSON request body field — asset IDs to be set on the Action Plan
status_idNoJSON request body field — action Plan Status ID to be set on the Action Plan
manager_idNoJSON request body field — party Person ID of the Action Plan Manager
project_idYesURL path parameter — unique identifier for the project.
descriptionNoJSON request body field — description of the Action Plan
location_idNoJSON request body field — location ID to be set on the Action Plan
plan_type_idNoJSON request body field — plan Type ID to be set on the Action Plan
plan_approvers_attributesNoJSON request body field — plan_approvers_attributes
plan_receivers_attributesNoJSON request body field — plan_receivers_attributes
custom_field_%{custom_field_definition_id}NoJSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description adds substantial behavioral detail: omitted fields retain their values, the request payload nests fields under 'plan', project_id defaults from procore_set_config, and failures return HTTP statuses (401, 403, 404). This fully discloses the operation's side effects and error modes.

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 dense but well-structured: action, update semantics, payload wrapping, defaults, id resolution, return value, error handling, required parameters, and API endpoint. Every sentence adds value, though it is longer than ideal; the complexity justifies the length.

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

Completeness5/5

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

The description covers the operation, prerequisites (resolve id), return value, error conditions, default behavior, API category, and endpoint. With no output schema, the description fully explains the response and failure modes. It is complete for a tool of this complexity.

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 input schema already provides 100% per-parameter descriptions. The description adds extra meaning by explaining that request body fields are passed as top-level arguments and wrapped into the 'plan' object, and that project_id defaults to the configured value. It also clarifies that id must be resolved via a list tool, which is not in 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 'Updates an existing action plan in the specified Procore project', which is a specific verb+resource. It distinguishes from related tools like create_action_plan or delete_action_plan by explicitly targeting existing plans and providing the PATCH endpoint.

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 provides clear context for when to use the tool: it's for updating existing action plans, and it instructs to 'resolve it with the matching list tool first'. It also explains the partial update behavior ('Send only the fields you intend to change') but does not explicitly mention alternatives like create_action_plan for new plans.

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