Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Action Plans

list_action_plans
Read-onlyIdempotent

Retrieve a paginated list of action plans for a project. Filter by ID, plan type, manager, location, or date ranges.

Instructions

List of all Action Plans. 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/plans

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__include_sublocationsNoQuery string parameter — use together with `filters[location_id]`
filters__location_idNoQuery string parameter — location ID. Returns item(s) with the specified Location ID or a range of Location IDs.
filters__manager_idNoQuery string parameter — return item(s) with a specific Manager ID or a range of Manager ID(s).
filters__plan_type_idNoQuery string parameter — action Plan Type ID. Returns item(s) with the specified Action Plan Type ID(s).
filters__template_idNoQuery string parameter — return Action Plan(s) associated with the specified Action Plan Template 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...
sortNoQuery string parameter — direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter.
Behavior4/5

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

Annotations provide readOnlyHint=true, so no contradiction. Description adds value by explaining pagination behavior, return format (JSON array with metadata), and endpoint info, which are beyond 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?

The description is 5 sentences, front-loaded with purpose, and each sentence adds value: purpose, usage, return format, pagination, required param, API reference. No fluff.

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

Completeness4/5

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

Given the complexity (12 params, paginated list) and high schema coverage, the description covers essential aspects: action, pagination, required param, endpoint. It mentions return includes metadata. Lacks details on each filter but schema compensates. Almost complete.

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%, so baseline 3. Description mentions required project_id and pagination params but does not detail filter parameters. Schema already describes them well, so description adds minimal extra meaning.

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 the tool lists all Action Plans, enumerates its use for paginated overview, finding IDs, and filtering. It distinguishes from siblings like create/update/delete by explicitly stating it lists.

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 on when to use (enumerate, find IDs, filter) and mentions required parameter project_id. It does not explicitly state when not to use (e.g., for a single plan use show_action_plan), but the sibling context suggests alternatives.

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