Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Action Plan Sections

list_action_plan_sections
Read-onlyIdempotent

Retrieve action plan sections for a Procore project. Filter by plan or ID, paginate results, and include nested plan items with the extended view.

Instructions

Returns all Action Plan Sections for a given Project. View Parameter: - normal (default): Returns standard Action Plan Section attributes - extended: Returns standard attributes plus nested plan_items array - ids: Returns an array of Action Plan Section IDs only. Use this to discover action plan sections or to look up the id of one before calling a tool that needs it. project_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of action plan sections; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. 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. Procore API: Project Management > Action Plans. Endpoint: GET /rest/v1.0/projects/{project_id}/action_plans/plan_sections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
viewNoQuery string parameter — specifies which view (which attributes) of the Action Plan Section is going to be present in the response. - `normal` (default): Returns standard Action Plan Section attributes - `extended`: Return...
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__plan_idNoQuery string parameter — return item(s) associated with the specified Action Plan ID(s)
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__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...
Behavior5/5

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

The description discloses read-only behavior ('it changes nothing in Procore'), error handling (401, 403, 404 statuses), pagination details, and the default project_id behavior. These add value beyond the annotations, which already indicate read-only and non-destructive hints.

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 moderately long but well-structured, starting with a summary, then view details, defaults, return format, and error handling. Each sentence earns its place, though it could be slightly more concise.

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?

With no output schema, the description provides return format ('JSON array of action plan sections'), pagination info, error handling, and usage examples. It is comprehensive enough for the 8-parameter tool and the annotations cover safety, making it highly complete.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds extra meaning by detailing the view parameter options and noting that project_id defaults to the procore_set_config value when omitted, 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 'Returns all Action Plan Sections for a given Project' with a specific verb and resource. It distinguishes itself from sibling tools by focusing on Action Plan Sections and explaining the view parameter variants (normal, extended, ids).

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 explicit usage guidance: 'Use this to discover action plan sections or to look up the id of one before calling a tool that needs it.' This clarifies when to use the tool, though it does not mention alternatives or exclusions, so it doesn't earn a 5.

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