Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Action Plan Approvers

list_action_plan_approvers
Read-onlyIdempotent

Retrieve all action plan approvers for a specified Procore project. Use to discover approvers or get their IDs for subsequent API calls.

Instructions

Returns all Action Plan Approvers for a given Project. Use this to discover action plan approvers 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 approvers; 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_approvers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
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__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...
Behavior4/5

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

Beyond annotations, the description adds pagination behavior (page/per_page and remaining pages), default project_id handling, and detailed error payloads (401, 403, 404). These operational details help the agent anticipate possible outcomes.

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 reasonably concise, starting with the main purpose and then adding operational details. Every sentence contributes meaning, though the API reference and required-parameter reminder add minor repetition.

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?

Covers return type, pagination, default behavior, and common errors, which is sufficient for a straightforward list tool. Without an output schema, it could specify the structure of an approver object, but the description is otherwise 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 coverage is 100%, so all parameters already have descriptions. The description adds value by explaining the project_id default from procore_set_config and confirming that page/per_page control pagination, which supplements 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 the tool's function: 'Returns all Action Plan Approvers for a given Project.' It uses a specific verb and resource, and adds a use case ('discover action plan approvers or look up the id') that distinguishes it from siblings like list_action_plan_template_approvers.

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 context for when to use the tool ('Use this to discover action plan approvers or to look up the id of one before calling a tool that needs it') and notes it is read-only. It does not explicitly name alternatives or exclusions, but the guidance is clear enough.

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