Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Coordination Issues In Recycle Bin

list_coordination_issues_in_recycle_bin
Read-onlyIdempotent

Retrieve a paginated list of deleted coordination issues for a project. Filter by assignee, status, or date to find specific issues.

Instructions

Lists all deleted Coordination Issues in 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/recycle_bin

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...
filters__overdueNoQuery string parameter — filter item(s) with matching Overdue.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that the tool returns a 'paginated JSON array of Coordination Issues' with pagination metadata, and mentions required parameters and endpoint details. This provides context beyond the annotations.

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 four sentences, front-loaded with the main purpose. It is concise and provides essential information without unnecessary fluff. The inclusion of API endpoint is slightly extra but not wasteful.

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 complexity (22 parameters, no output schema), the description covers the basic functionality, pagination, required parameters, and even mentions the API endpoint. It does not describe the return format in detail, but the openWorldHint suggests the agent can explore. Fairly complete for a list tool.

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 mentions pagination parameters (page, per_page) and required project_id, but does not add significant meaning beyond the schema descriptions for the many filter parameters. It adds marginal value.

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 lists 'deleted Coordination Issues' in a specified project. The verb 'Lists' and the specific resource 'Coordination Issues in the Recycle Bin' are precise. This distinguishes it from other listing tools like 'list_coordination_issues' which retrieve active issues.

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 use cases: 'enumerate Coordination Issues when you need a paginated overview, to find IDs, or to filter by query parameters.' It implicitly distinguishes from tools that list non-deleted issues, but does not explicitly name alternatives or when not to use it.

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