Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Generic Tool Items

list_generic_tool_items
Read-onlyIdempotent

Retrieve a paginated list of custom-configurable tool items for a given project and generic tool. Use filters to find specific items by ID, status, or date.

Instructions

Returns a list of all Generic Tool Items in the specified Project and Generic Tool. For more information on Generic Tool and Correspondence Tool endpoints, see Working with the Correspondence Tool. Use this to enumerate Custom - Configurable Tools when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Custom - Configurable Tools. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: generic_tool_id, project_id. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.0/projects/{project_id}/generic_tools/{generic_tool_id}/generic_tool_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
generic_tool_idYesURL path parameter — unique identifier for the Generic Tool
project_idYesURL path parameter — unique identifier for the project.
viewNoQuery string parameter — if supplied customize the response format
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__login_information_idNoQuery string parameter — array of Login Information IDs. Returns item(s) with the specified Login Information ID.
filters__statusNoQuery string parameter — returns item(s) matching the specified status value.
filters__overdueNoQuery string parameter — if true, returns item(s) that are overdue.
filters__queryNoQuery string parameter — return item(s) containing search query
filters__recycle_binNoQuery string parameter — if true, returns item(s) that have been deleted.
filters__received_from_idNoQuery string parameter — filter results by received from id
filters__created_by_idNoQuery string parameter — returns item(s) created by the specified User IDs.
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...
filters__closed_atNoQuery string parameter — returns item(s) closed within the specified ISO 8601 datetime range.
filters__issued_atNoQuery string parameter — returns item(s) issued within the specified ISO 8601 datetime range.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor ID.
sortNoQuery string parameter — field to sort by. If the field is passed with a - (EX: -updated_at) it is sorted in reverse order
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: pagination details (page, per_page, metadata), filtering capability, required parameters, and the endpoint. It does not contradict any 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 concise with about four sentences, each adding key information: purpose, use cases, response format, and required params. It is front-loaded with the most important info and contains no unnecessary words.

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 19 parameters and no output schema, the description covers purpose, usage, pagination, required params, and includes a documentation link. It could briefly mention typical response fields, but overall it is complete for a list endpoint.

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 description coverage is 100%, so the schema already documents all parameters. The description mentions 'page and per_page' for pagination and lists required parameters, but adds limited new meaning beyond the schema. Baseline 3 is appropriate.

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 returns a list of Generic Tool Items for a specific Project and Generic Tool. It uses specific verbs like 'list', 'enumerate', and explains the resource type. It distinguishes from siblings by focusing on 'enumerate' and 'paginated overview', which differentiates it from update/create tools.

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 explicit use cases: 'to enumerate... when you need a paginated overview, to find IDs, or to filter by query parameters.' However, it does not specify when not to use this tool or mention alternatives among the many sibling tools. This is a clear context but lacks exclusions.

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