Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_of_deleted_submittals

Retrieve deleted submittals from the recycle bin in Procore projects to review, restore, or audit removed documents.

Instructions

List of deleted Submittals. [Project Management/Submittals] GET /rest/v1.0/projects/{project_id}/submittals/recycle_bin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
pageNoPage
per_pageNoElements per page
filters__idNoReturn item(s) with the specified IDs.
filters__ball_in_court_idNoUser ID. Return item(s) where the specified User ID is the Ball in Court.
filters__created_atNoReturn 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-...
filters__queryNoReturn item(s) containing search query
filters__received_from_idNoReceived From ID
filters__responsible_contractor_idNoArray of Responsible Contractor IDs. A single Responsible Contractor ID is also accepted.
filters__specification_section_idNoArray of Specification Section IDs. A single Specification Section ID is also accepted.
filters__approver_idNoArray of User IDs. Return item(s) where the specified User IDs are in the approver list. A single integer is also accepted.
filters__current_revisionNoDefault false. If true, only current revisions are shown. If false, all submittals are shown, regardless of whether or not it is the current revision.
filters__divisionNoArray of Divisions to filter on. A Division is the first two digits from the Specification Section Number. A single Division is also accepted.
filters__location_idNoArray of Location IDs. A single Location ID is also accepted.
filters__submittal_manager_idNoArray of Submittal Manager IDs. A single Submittal Manager ID is also accepted.
filters__submittal_package_idNoArray of Submittal Package IDs. Returns item(s) associated with the specified Submittal Package IDs. A single integer value is also accepted.
filters__response_idNoArray of Response IDs. A single Response ID is also accepted.
filters__status_idNoArray of Status IDs. A single Status ID is also accepted.
filters__typeNoArray of Submittal Types. A single Submittal Type is also accepted.
filters__updated_atNoReturn 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...
sortNosort
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'List of deleted Submittals' which implies a read-only operation, but doesn't disclose pagination behavior (implied by page/per_page parameters), authentication needs, rate limits, or what 'deleted' means (soft delete vs permanent). The HTTP method (GET) is mentioned but not explained.

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 a single sentence with zero waste, directly stating the purpose. It includes the API endpoint path which is somewhat redundant but not overly verbose. However, it could be more front-loaded by emphasizing key constraints.

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

Completeness2/5

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

For a tool with 21 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the return format, pagination behavior, error conditions, or what 'deleted' entails. The agent lacks sufficient context to use this tool effectively beyond basic parameter passing.

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 fully documents all 21 parameters. The description adds no parameter-specific information beyond what's in the schema. The baseline is 3 because the schema does the heavy lifting, but the description doesn't compensate with any additional context about filter usage or sorting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('deleted Submittals'), making the purpose explicit. It distinguishes from non-deleted submittal tools by specifying 'deleted', though it doesn't explicitly differentiate from sibling tools like 'list_of_deleted_submittals_v1_1'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for accessing deleted items, or how it differs from other submittal listing tools. The agent must infer usage from the name alone.

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