Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Coordination Issues Workflow Issues

list_coordination_issues_workflow_issues
Read-onlyIdempotent

Get a paginated list of coordination issues with workflow metadata, filtered by user permissions. Use to find issue IDs, apply filters by status, assignee, or other parameters.

Instructions

Returns a list of Coordination Issues that have associated workflow metadata. Issues are filtered based on user visibility rules: - Project Admins can see all workflow issues - Issue creators can see issues they created - Issue assignees can see issues assigned to them - Workflow members can see issues for workflows they are part of. 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/workflow_issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
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__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__idNoQuery string parameter — filter by specific Coordination Issue 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__source_file_idNoQuery string parameter — filter by source BIM file ID
viewNoQuery string parameter — specifies the view to use for the response. Use 'normal' for basic fields, 'extended' for full details including viewpoints and attachments.
viewpoint_formatNoQuery string parameter — specifies the format for viewpoint data. Use 'procore' for Procore format, 'bcf' for BCF format.
includedNoQuery string parameter — comma-separated list of fields to include in the response.
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds significant behavioral context: visibility rules (project admins, creators, assignees, workflow members), pagination, required parameters, and endpoint info. 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?

The description is very concise, front-loaded with the main purpose, uses bullet points for visibility rules, and every sentence adds value. No 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 tool has 27 parameters and no output schema, the description covers visibility rules, pagination, required parameters, and endpoint. It could be more explicit about the return fields (workflow metadata), but it still provides a reasonably complete overview.

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%, baseline 3. The description adds meaning by mentioning required parameters (company_id, project_id), the pagination control parameters (page, per_page) and that the response includes pagination metadata. This adds value beyond the schema.

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 Coordination Issues with workflow metadata, distinguishes it from similar tools by specifying scope (only issues with workflow metadata) and visibility rules. It is specific and unique.

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 provides explicit usage context: 'Use this to enumerate Coordination Issues when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not explicitly state when not to use it or name alternatives, but the context is clear.

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