Skip to main content
Glama
TylerIlunga

Procore MCP Server

Download Coordination Issues

download_coordination_issues
Read-onlyIdempotent

Export coordination issues to BCF, CSV, or PDF with optional filters. Retrieve full issue data read-only from Procore.

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 when you already know which coordination issue you want and need its full field set. Returns a JSON object containing the generated file or a download URL for the coordination issue. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. 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
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 — response detail level. Use 'normal' for standard fields or 'extended' for all fields
project_idYesQuery string parameter — unique identifier for the project.
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 ...
export_formatYesQuery string parameter — export File Format.
filters__ids__NoQuery string parameter — filter item(s) with matching ids.
filters__searchNoQuery string parameter — filter item(s) with the matching search query. The search is performed on title and issue number.
filters__overdueNoQuery string parameter — filter item(s) with matching Overdue.
filters__status__NoQuery string parameter — filter item(s) with matching status.
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__issue_type__NoQuery string parameter — filter item(s) with matching issue_type.
filters__assignee_id__NoQuery string parameter — filter item(s) with matching assignees.
filters__location_id__NoQuery string parameter — filter item(s) with matching locations.
filters__assignee_company_id__NoQuery string parameter — filter item(s) with matching assignee vendor companies.
filters__created_by_company_id__NoQuery string parameter — filter item(s) with matching created by vendor companies.
filters__coordination_issue_file_id__NoQuery string parameter — filter item(s) with the exact coordination issue file.
Behavior5/5

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

Annotations already declare readOnlyHint=true, but the description adds substantial behavioral context: BCF export restrictions (only issues with snapshot/valid camera data), error payload details (401/403/404), and return format (JSON object or download URL). These go beyond annotation hints and help the agent handle failures and edge cases.

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 moderately long but each sentence adds value: purpose, BCF limitation, usage context, return value, read-only guarantee, error handling, and required parameters. The API path reference is slightly extraneous, but overall it is efficiently structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an export tool with 18 parameters and no output schema, the description covers the essential aspects: what it does, how to scope, format-specific behavior, return type, safety guarantee, and common error responses. It is complete enough for an AI agent to select and invoke the tool correctly.

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 description coverage is 100%, so the schema already documents all parameters in detail. The description only mentions required parameters and generic filter scoping, which does not add meaning beyond the schema. Baseline score of 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?

The description clearly states the action (downloads coordination issues to a file) and specifies the export format. It distinguishes from sibling tools like 'list_coordination_issues' by emphasizing export and full field set. The BCF-specific behavior further clarifies scope.

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 a clear use case: 'Use this when you already know which coordination issue you want and need its full field set.' This implies when not to use it (e.g., when you need a list or don't know specific issues). However, it does not explicitly name alternative tools or exclusion criteria, so it's slightly below a 5.

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