Skip to main content
Glama
TylerIlunga

Procore MCP Server

Download Coordination Issues

download_coordination_issues
Read-onlyIdempotent

Download coordination issues to your preferred format (BCF, CSV, or PDF). Use filters to scope the export by assignee, status, location, and more.

Instructions

Downloads coordination issues to a file specified by the export format. The items to be exported can be scoped by using filters. BCF export will only export the issues with a snapshot and valid camera data. Use this to retrieve a downloadable file or export URL for Coordination Issues. Returns a JSON object with the file contents or download URL for Coordination Issues. Required parameters: project_id, export_format. Procore API: Project Management > Coordination Issues. Endpoint: GET /rest/v1.0/coordination_issues/export

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
filters__assignee_company_id__NoQuery string parameter — filter item(s) with matching assignee vendor companies.
column_stateNoQuery string parameter — optional array of column configuration objects from frontend table state. Allows export to respect custom column visibility and ordering. Each object should have a 'field' property with the column ...
filters__assignee_id__NoQuery string parameter — filter item(s) with matching assignees.
filters__ids__NoQuery string parameter — filter item(s) with matching ids.
filters__location_id__NoQuery string parameter — filter item(s) with matching locations.
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__updated_atNoQuery string parameter — filter item(s) within a specific updated at iso8601 datetime range.
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__overdueNoQuery string parameter — filter item(s) with matching Overdue.
viewNoQuery string parameter — response detail level. Use 'normal' for standard fields or 'extended' for all fields
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 '-'
export_formatYesQuery string parameter — export File Format.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

The description reveals that the tool returns a JSON object with file contents or a download URL, and notes the BCF export condition. It does not contradict the annotations (readOnlyHint, idempotentHint, etc.). While annotations already indicate read-only and idempotent behavior, the description adds context about the return format and export limitations.

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 relatively concise, using two main sentences plus a BCF-specific note and return type statement. It redundantly repeats 'Coordination Issues' and includes Procore API endpoint info which may not be essential, but overall it is front-loaded with the primary action.

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's complexity (19 parameters) and the presence of detailed schema descriptions, the description adequately covers the core purpose, return format, and a key export condition. However, it does not elaborate on all filters or export formats, relying on the schema for those details. The lack of an output schema is partially mitigated by the description mentioning a JSON return.

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?

The input schema has 100% description coverage for all 19 parameters. The description adds only minor extra semantics by highlighting the required parameters (project_id, export_format) and the BCF snapshot requirement. With high schema coverage, the baseline is 3, and the description does not significantly enhance parameter understanding.

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 downloads coordination issues to a file based on export format, with scoping via filters. It distinguishes itself from sibling tools like list_coordination_issues by explicitly focusing on export/download functionality.

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 clear guidance on when to use the tool (to retrieve a downloadable file or export URL) and notes required parameters (project_id, export_format). It also specifies a condition for BCF export. However, it does not explicitly compare with alternative download tools or state when not to use this tool.

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