Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Correspondence Type Items

list_correspondence_type_items
Read-onlyIdempotent

Fetch a paginated list of correspondence type items for a project. Use filters to narrow results by ID, status, date, or other criteria.

Instructions

Returns a list of all Correspondence Type Items in the specified Project. 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: project_id. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.0/projects/{project_id}/correspondence_type_items

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__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__generic_tool_idNoQuery string parameter — return item(s) within the specified Generic Tool ID(s)
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.
filters__privateNoQuery string parameter — if true, returns only item(s) with a `private` status.
filters__location_idNoQuery string parameter — filters by specific location (Note: Use *either* this or location_id_with_sublocations, but not both)
sortNoQuery string parameter — field to sort by. If the field is passed with a - (EX: -updated_at) it is sorted in reverse order
groupNoQuery string parameter — controls if the Items are returned sorted by the sort attribute then the Generic Tool's Title or just the sort attribute. Defaults to 'generic_tool_title'.
viewNoQuery string parameter — defines the type of view returned. Must be one of 'extended', 'compact', 'ids_only', or 'flatten_v0'.
Behavior4/5

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

Annotations indicate read-only, destructive=false, idempotent. Description adds that it returns a paginated JSON array with pagination metadata, which is beyond annotations. No contradictions.

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?

Four sentences that are front-loaded with purpose, include a link, and provide essential details without redundancy or wasted 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 the large number of parameters, no output schema, and presence of annotations, the description adequately covers pagination behavior, required parameter, and filtering capabilities. A link to tutorial adds completeness, though more detail on common filters could be included.

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 has 100% coverage with descriptions for all 22 parameters. Description only highlights project_id as required and mentions page/per_page for pagination, adding little beyond 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?

Clearly states it returns a list of Correspondence Type Items for a project, with specific use cases like paginated overview and ID finding. Distinguishes from other list endpoints by specifying the resource type.

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 when-to-use guidance (enumerate Custom-Configurable Tools, paginated overview, find IDs, filter). Includes a link to further documentation, though it lacks explicit when-not-to-use or 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