Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Coordination Issues

list_coordination_issues
Read-onlyIdempotent

Retrieve a paginated list of coordination issues for a project. Use filters to narrow by status, assignee, or other fields.

Instructions

Lists Coordination Issues associated with the specified Project. Use this to enumerate Coordination Issues when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Coordination Issues. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Coordination Issues. Endpoint: GET /rest/v1.0/coordination_issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string 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__assignee_company_id__NoQuery string parameter — filter item(s) with matching assignee vendor companies.
filters__assignee_id__NoQuery string parameter — filter item(s) with matching assignees.
filters__created_by_id__NoQuery string parameter — filter item(s) with matching User IDs.
filters__created_from__NoQuery string parameter — filter item(s) with matching creation source.
filters__ids__NoQuery string parameter — filter item(s) with matching ids.
filters__location_id__NoQuery string parameter — filter item(s) with matching locations.
filters__include_sublocationsNoQuery string parameter — use together with `filters[location_id]`
filters__searchNoQuery string parameter — filter item(s) with the matching search query. The search is performed on title and issue number.
filters__coordination_issue_file_id__NoQuery string parameter — filter item(s) with the exact coordination issue file.
filters__status__NoQuery string parameter — filter item(s) with matching status.
filters__issue_type__NoQuery string parameter — filter item(s) with matching issue_type.
filters__priority__NoQuery string parameter — filter item(s) with matching priority.
filters__trade_id__NoQuery string parameter — filter item(s) with matching trades.
filters__updated_atNoQuery string parameter — filter item(s) within a specific updated at iso8601 datetime range.
filters__due_dateNoQuery string parameter — filter item(s) within a specific due date iso8601 date range.
filters__created_atNoQuery string parameter — filter item(s) within a specific created at iso8601 datetime range.
sortNoQuery string parameter — sort item(s) by an attribute. The default sort is ascending. To sort in descending order, prepend the sort value with a hyphen character '-'
viewNoQuery string parameter — the compact view contains only ids. The normal view is a subset of the response shown below, and does not include attachments, viewpoints, linked items and updated_by The extended view contains the...
viewpoint_formatNoQuery string parameter — specify viewpoint data format. This parameter functions only when the query parameter view is 'extended' The default format returns the viewpoint content as saved. The procore format returns the vi...
filters__overdueNoQuery string parameter — filter item(s) with matching Overdue.
filters__document_container_id__NoQuery string parameter — filter Coordination Issues by document container ID(s).
filters__document_revision_id__NoQuery string parameter — filter Coordination Issues by document revision ID(s).
save_sticky_filtersNoQuery string parameter — persists filter parameters for the requesting user and project.
Behavior4/5

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds behavioral details about pagination (page/per_page) and response format (JSON array with metadata). It does not contradict annotations and provides useful context beyond what annotations offer.

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 concise, with the main action and use cases in the first sentence. It includes relevant API info. Some redundancy (e.g., mentioning 'paginated' twice) is minor. Front-loaded and efficient.

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?

The tool has 26 parameters with high schema coverage but no output schema. The description provides pagination and required parameter info, but doesn't explain common response fields (e.g., id, title, status). Given the complexity, slightly more detail on response structure would improve completeness.

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 coverage is 100%, so baseline is 3. The description adds value by highlighting the required parameter (project_id) and the pagination parameters, but does not elaborate on the many filter parameters. This is adequate given the schema descriptions.

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 it lists Coordination Issues for a project, with specific use cases (pagination, finding IDs, filtering). It also provides the endpoint and API section. However, it doesn't explicitly differentiate from sibling tools like 'list_coordination_issues_for_a_project_rest_v2_0', which might cause confusion about which version to use.

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 outlines when to use the tool: for a paginated overview, to find IDs, or to filter. It mentions required parameters. However, it does not provide when-not-to-use guidance or compare with alternatives, such as the v2 endpoint or the POST variant.

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