Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Coordination Issues For A Project (REST V2.0)

list_coordination_issues_for_a_project_rest_v2_0
Read-onlyIdempotent

Retrieve a paginated list of coordination issues in a project. Filter by status, assignee, location, and more, or use ids_only view to get just IDs.

Instructions

Returns a paginated list of coordination issues visible to the user within the project. Supports view=ids_only for { "data": [<id>, ...] } (JSON numbers from pluck(:id)). Query included controls which attributes are present on each item (see schema description). When save_sticky_filters is truthy, list filters may be persisted for the tool (sticky filters). 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: company_id, project_id. Procore API (v2.0): Project Management > Coordination Issues. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/coordination_issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
viewNoQuery string parameter — when `ids_only`, response is id list only (no full blueprint objects).
save_sticky_filtersNoQuery string parameter — when true, persist current filters for the coordination issues tool where supported.
includedNoQuery string parameter — comma-separated blueprint field names (e.g. `assignee,title,uuid,location`). When omitted or empty, all conditional fields are included.
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_idNoQuery string parameter — filter item(s) with matching assignee vendor companies.
filters__assignee_idNoQuery string parameter — filter item(s) with matching assignee user IDs.
filters__created_by_idNoQuery string parameter — return item(s) created by the specified User IDs
filters__created_fromNoQuery string parameter — filter item(s) by creation source.
filters__idsNoQuery string parameter — return only coordination issues with these ids (see `CoordinationIssues::Filter` / `with_ids`).
filters__location_idNoQuery string parameter — filters by specific location (Note: Use *either* this or location_id_with_sublocations, but not both)
filters__include_sublocationsNoQuery string parameter — use together with `filters[location_id]`
filters__searchNoQuery string parameter — returns item(s) matching the specified search query string.
filters__statusNoQuery string parameter — return item(s) with the specified statuses
filters__issue_typeNoQuery string parameter — filter item(s) by issue type.
filters__priorityNoQuery string parameter — filter item(s) by priority level.
filters__trade_idNoQuery string parameter — filter results by trade id
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__due_dateNoQuery string parameter — filter Coordination Issues by due date.
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-...
sortNoQuery string parameter — sort results by field. Direction (asc/desc) controlled by presence or absence of '-' prefix.
filters__overdueNoQuery string parameter — filter for overdue Coordination Issues.
filters__document_container_idNoQuery string parameter — filter Coordination Issues by document container ID(s).
filters__document_revision_idNoQuery string parameter — filter Coordination Issues by document revision ID(s).
filters__coordination_issue_file_idNoQuery string parameter — filter by BIM / coordination issue file id(s).
filters__watcher_idNoQuery string parameter — filter by watcher user id(s).
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description appropriately adds context about pagination, the ids_only view, sticky filters, and pagination metadata. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose and front-loads key behaviors. It is clear and well-structured, though slightly verbose with some redundancy (e.g., repeated mention of pagination).

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 lack of an output schema, the description adequately explains the return format (paginated JSON array with metadata) and covers key behaviors. It is reasonably complete for a list tool with many parameters.

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%, but the description adds value by explaining how the `view` and `included` parameters affect the response, and the role of `save_sticky_filters`. This goes beyond the schema's per-field descriptions.

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 it returns a paginated list of coordination issues for a project, specifying the resource and scope. The title includes the API version, distinguishing it from other list tools like the recycle bin variant.

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?

The description explicitly says when to use the tool: for a paginated overview, to find IDs, or to filter by query parameters. While it does not mention alternatives by name, the guidance is clear and actionable.

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