Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Action Plan Items

list_action_plan_items
Read-onlyIdempotent

List action plan items for a project. Filter results by query, status, assignee, due date, and reference IDs with pagination.

Instructions

Returns all Action Plan Items for a given Project. Use this to enumerate Action Plans when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Action Plans. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Action Plans. Endpoint: GET /rest/v1.0/projects/{project_id}/action_plans/plan_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__created_atNoQuery string parameter — return item(s) created within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-...
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__plan_section_idNoQuery string parameter — return item(s) associated with the specified Action Plan Section(s).
filters__plan_idNoQuery string parameter — return item(s) associated with the specified Action Plan ID(s)
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
filters__queryNoQuery string parameter — return item(s) containing search query
filters__due_atNoQuery string parameter — return item(s) due within the specified date range.
filters__assignee_party_id_or_role_idNoQuery string parameter — return item(s) associated with the specified Action Plan Assignee party ID(s) or role ID(s)
filters__attachment_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference attachment ID(s)
filters__drawing_revision_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference drawing revision ID(s)
filters__file_version_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference file version ID(s)
filters__plan_test_record_request_idNoQuery string parameter — return item(s) associated with the specified Action Plan Test Record Request ID(s).
filters__specification_section_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference specification section id ID(s)
filters__verification_method_idNoQuery string parameter — return item(s) associated with the specified Action Plan Assignee verification method ID(s)
filters__generic_tool_item_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference Generic Tool Item ID(s)
filters__form_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference Form ID(s)
filters__meeting_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference Meeting ID(s)
filters__observation_item_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference Observation Item ID(s)
filters__submittal_log_idNoQuery string parameter — return item(s) associated with the specified Action Plan reference submittal log ID(s)
filters__record_checklist_template_idNoQuery string parameter — return item(s) with the specified checklist template id.
filters__record_generic_tool_idNoQuery string parameter — return item(s) with the specified Generic Tool ID.
filters__reference_typeNoQuery string parameter — return item(s) associated with the specified Action Plan reference type(s)
filters__status_idNoQuery string parameter — array of Status IDs. A single Status ID is also accepted.
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds pagination details (page, per_page, metadata) and mentions the Procore API endpoint, fully aligning with annotations.

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

Conciseness5/5

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

Four sentences, front-loaded with purpose, then usage, then pagination, then API reference. No redundancy or unnecessary words.

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?

Lacks an explanation of what an Action Plan Item is or the structure of the response (no output schema). Also could elaborate on filtering capabilities given 26 parameters. Minor inconsistency: describes results as 'Action Plans' instead of 'Action Plan Items'.

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%; description adds minimal value beyond mentioning required project_id and pagination controls. Baseline 3 is appropriate as schema already explains parameters.

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

Purpose4/5

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

Clearly states it returns all Action Plan Items for a given Project with pagination and filtering. However, it does not explicitly differentiate this tool from sibling tools like list_action_plans or list_action_plan_sections.

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?

Provides specific usage scenarios: enumerating with pagination, finding IDs, filtering. Missing guidance on when not to use or explicit alternatives, but still offers actionable context.

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