Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Action Plan Item

create_action_plan_item

Create a new action plan item for a Procore project's action plan section. Required parameters: project ID, section ID, and title.

Instructions

Creates an Action Plan Item for a given Action Plan Section. Use this to create a new Action Plans in Procore. Creates a new Action Plans and returns the created object on success (HTTP 201). Required parameters: project_id, plan_section_id, title. Procore API: Project Management > Action Plans. Endpoint: POST /rest/v1.0/projects/{project_id}/action_plans/plan_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
plan_section_idYesJSON request body field — section ID of the Action Plan Item
titleYesJSON request body field — title of the Action Plan Item
descriptionNoJSON request body field — description of the Action Plan Item
notesNoJSON request body field — notes for the Action Plan Item
due_atNoJSON request body field — due Date of the Action Plan Item
holding_typeNoJSON request body field — action Plan Item holding type specifies whether the current item holds all the succeeding items in the section or the plan
Behavior3/5

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

Annotations already indicate non-read-only, non-destructive, non-idempotent. Description adds that it returns the created object on HTTP 201, which is helpful. However, it doesn't disclose other behavioral traits like field validation, error handling, or 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?

Description is three sentences but includes redundant API info and a typo. Could be more concise and front-loaded with key actions.

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?

Given 7 parameters and no output schema, the description fails to explain optional parameter behavior, error responses, or relationships between fields. Lacks completeness for an agent to invoke confidently.

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?

Input schema has 100% coverage with descriptions for all 7 parameters. The description lists required parameters but does not explain optional ones, behaviors, or the enum holding_type. No additional meaning beyond schema.

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

Purpose3/5

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

The description states it creates an Action Plan Item, but includes typos like 'create a new Action Plans' which creates confusion. It does not distinguish from sibling tools like bulk_create_action_plan_item_assignees or create_action_plan_section.

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?

No explicit guidance on when to use this tool versus alternatives such as bulk_create_action_plan_items. Does not mention when not to use it or prerequisites beyond required params.

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