Skip to main content
Glama
TylerIlunga

Procore MCP Server

Return A List Of All Submittals.

return_a_list_of_all_submittals
Read-onlyIdempotent

Retrieve a paginated list of submittals from a Procore project. Filter by ID, status, date range, and more to get specific submittal data.

Instructions

Return a list of all Submittals. Use this to read information about Submittals from Procore. Returns a paginated JSON array of Submittals. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Submittals. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/submittals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path 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__idNoQuery string parameter — return item(s) with the specified IDs.
filters__anticipated_delivery_dateNoQuery string parameter — array of dates (date range). Returns item(s) with their anticipated delivery date within the specified dates. A single date is also accepted. style: form
filters__ball_in_court_idNoQuery string parameter — user ID. Return item(s) where the specified User ID is the Ball in Court.
filters__ball_in_court_company_idNoQuery string parameter — company ID. Return item(s) where the specified Company ID is the Ball in Court.
filters__closed_atNoQuery string parameter — return item(s) that are due 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__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__queryNoQuery string parameter — return item(s) containing search query
filters__received_from_idNoQuery string parameter — filter results by received from id
filters__responsible_contractor_idNoQuery string parameter — return item(s) with the specified Responsible Contractor ID.
filters__specification_section_idNoQuery string parameter — array of Specification Section IDs. A single Specification Section ID is also accepted.
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__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__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__location_idNoQuery string parameter — array of Location IDs. A single Location ID is also accepted.
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__response_idNoQuery string parameter — array of Response IDs. A single Response ID is also accepted.
filters__status_idNoQuery string parameter — array of Status IDs. A single Status ID is also accepted.
filters__typeNoQuery string parameter — array of Submittal Types. A single Submittal Type is also accepted.
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__unpackagedNoQuery string parameter — parseable to boolean value, filters out unpackaged Submittals.
filters__numberNoQuery string parameter — array of Numbers. A single Number is also accepted.
filters__has_operation_errorsNoQuery string parameter — parseable to boolean value, filters Submittals based on whether they have operation errors from bulk operations.
filters__operation_errors_by_operation_idNoQuery string parameter — filters Submittals that have operation errors associated with specific operation ID(s). Accepts single or multiple operation IDs.
sortNoQuery string parameter — structure to sort submittal rows
show_attachmentsNoQuery string parameter — determine the AttachmentVisible tag value(depend on configurable field set).
Behavior4/5

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

Annotations already indicate read-only and idempotent. The description adds value by explaining pagination behavior (page, per_page, metadata) and the API endpoint. No contradictions.

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?

Two sentences, front-loaded with purpose and key usage details. Every sentence is necessary and concise without waste.

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 (30 parameters, many siblings), the description is adequate: it covers pagination, required params, and return type. It could mention the extensive filter capabilities, but the schema compensates.

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 required parameters and pagination controls, adding minimal value beyond the schema.

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 it returns a list of Submittals, with a specific verb and resource. However, it does not differentiate from sibling tools like 'list_submittals' or 'list_submittals_on_a_project', which could cause confusion.

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

Usage Guidelines3/5

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

The description says 'Use this to read information about Submittals,' providing a general use case. But it offers no guidance on when to use this tool versus similar alternatives, nor does it specify 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