Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Action Plan Test Record Requests

list_action_plan_test_record_requests
Read-onlyIdempotent

Retrieve a paginated list of Action Plan Test Record Requests for a project. Filter by item IDs, plan IDs, types, creation, or update dates to find specific records.

Instructions

List of all Action Plan Test Record Requests. 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_test_record_requests

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
filters__plan_item_idNoQuery string parameter — return item(s) associated with the specified Action Plan Item 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__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__typeNoQuery string parameter — return item(s) associated with the specified Action Plan Test Record Type(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...
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
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 already declare readOnlyHint, idempotentHint, etc. The description adds value by explaining pagination behavior and return format, and it does not contradict annotations.

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 with four sentences, front-loading the purpose. It could be slightly tighter but is not verbose.

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?

Given the lack of output schema, the description mentions paginated JSON array and metadata, but does not detail error handling, authentication, or the structure of individual items. It covers the main points but could be more 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?

The input schema has 100% description coverage for all parameters. The description adds minimal extra meaning beyond noting pagination control and required project_id. Baseline 3 is appropriate.

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?

The description clearly states 'List of all Action Plan Test Record Requests' and explains its use for enumeration and filtering. However, it slightly conflates 'Action Plans' with 'Test Record Requests' by saying 'enumerate Action Plans,' which may cause confusion about the exact resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context for when to use the tool (paginated overview, find IDs, filter), but does not mention when not to use it or offer alternatives like list_action_plans for actual plan enumeration. The usage guidance is present but incomplete.

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