Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Of Deleted Submittals

list_of_deleted_submittals
Read-onlyIdempotent

Lists deleted submittals in a Procore project to help you locate removed records and retrieve their IDs for recovery or audit.

Instructions

The Submittals endpoint returns all deleted Submittals in a project. Use this to discover deleted submittals or to look up the id of one before calling a tool that needs it. project_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of deleted submittals; page and per_page control pagination and the response reports how many pages remain. 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. Procore API (v1.1): Project Management > Submittals. Endpoint: GET /rest/v1.1/projects/{project_id}/submittals/recycle_bin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__typeNoQuery string parameter — array of Submittal Types. A single Submittal Type is also accepted.
filters__queryNoQuery string parameter — return item(s) containing search query
filters__divisionNoQuery string parameter — array of Divisions to filter on. A Division is the first two digits from the Specification Section Number. A single Division is also accepted.
filters__status_idNoQuery string parameter — array of Status IDs. A single Status ID is also accepted.
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-...
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__approver_idNoQuery string parameter — array of User IDs. Return item(s) where the specified User IDs are in the approver list. A single integer is also accepted.
filters__location_idNoQuery string parameter — array of Location IDs. A single Location ID is also accepted.
filters__response_idNoQuery string parameter — array of Response IDs. A single Response ID is also accepted.
filters__ball_in_court_idNoQuery string parameter — user ID. Return item(s) where the specified User ID is the Ball in Court.
filters__current_revisionNoQuery string parameter — default 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__received_from_idNoQuery string parameter — filter results by received from id
filters__submittal_manager_idNoQuery string parameter — array of Submittal Manager IDs. A single Submittal Manager ID is also accepted.
filters__submittal_package_idNoQuery string parameter — array of Submittal Package IDs. Returns item(s) associated with the specified Submittal Package IDs. A single integer value is also accepted.
filters__specification_section_idNoQuery string parameter — array of Specification Section IDs. A single Specification Section ID is also accepted.
filters__responsible_contractor_idNoQuery string parameter — array of Responsible Contractor IDs. A single Responsible Contractor ID is also accepted.
Behavior5/5

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

Even with annotations declaring readOnlyHint and idempotentHint, the description adds valuable behavioral context: it describes pagination behavior and response metadata, the project_id default from procore_set_config, and common error scenarios (401, 403, 404) with their meaning. This goes well beyond the structured annotations and helps the agent anticipate 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph that is front-loaded with the core purpose, then efficiently covers return type, pagination, read-only nature, default behavior, error handling, required parameters, and API source. Each sentence carries essential information with no fluff or repetition.

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 a list endpoint with 21 parameters and no output schema, the description is remarkably complete: it states the return type (JSON array), pagination mechanism, error payload format, default project_id behavior, and the exact API endpoint. It does not enumerate each parameter (schema does that), but it gives enough context for an agent to invoke the tool correctly and understand the response shape.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema by explaining that project_id defaults to the procore_set_config value when omitted and that page/per_page control pagination in a way that reports remaining pages. This adds value on top of the schema's per-parameter descriptions.

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?

Description states a specific verb ('returns') and resource ('all deleted Submittals in a project'), clearly distinguishing it from sibling tools that list active submittals. It also gives a concrete use case: discovering deleted submittals or looking up an ID for another tool, which fully clarifies purpose.

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 explicitly states when to use the tool ('to discover deleted submittals or to look up the id of one before calling a tool that needs it'). It does not explicitly name alternative tools or state when not to use it, but the context of deleted submittals is clearly different from active submittal listers among siblings.

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