Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Submittals On A Project

list_submittals_on_a_project
Read-onlyIdempotent

Retrieve a paginated list of submittals from a specified Procore project, with filtering by ID, status, location, and more. Use to find submittal IDs or generate overviews.

Instructions

Return a list of all Submittals from a specified Project. See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. See Downloading attachments with markup for information on downloading attachments with markup as a PDF. Use this to enumerate Submittals when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Submittals. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API (v1.1): Project Management > Submittals. Endpoint: GET /rest/v1.1/projects/{project_id}/submittals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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__ball_in_court_idNoQuery string parameter — user ID. Return item(s) where the specified User ID is the Ball in Court.
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 — array of Responsible Contractor IDs. A single Responsible Contractor ID is also accepted.
filters__required_on_site_dateNoQuery string parameter — array of dates (date range). Returns item(s) with their required on site date withing the specified dates. A single date is also accepted. style: form
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__task_idNoQuery string parameter — array of Submittal Task IDs. Returns item(s) associated with the specified Submittal Task IDs. A single integer value is also accepted.
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
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral context: pagination (page and per_page), paginated JSON array with metadata, filtering capabilities via a link, and that it is a GET endpoint. This adds value beyond the annotations without contradiction.

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 well-structured, front-loaded with the main purpose, and includes necessary details like pagination, use cases, and API endpoint. While it includes URLs that could be considered extra, they are relevant. It is concise for the information provided.

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 rich input schema and lack of output schema, the description adequately explains the output (paginated JSON array with metadata) and mentions filtering via a link. It does not cover error conditions, but the overall context is sufficient for an AI agent to use 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?

With 100% schema description coverage, the baseline is 3. The description does not add new meaning to parameters beyond the schema, but it highlights the required parameter 'project_id' and provides links to filtering documentation. This is acceptable but not exceptional.

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 'Return a list of all Submittals from a specified Project,' specifying the verb and resource. It distinguishes from sibling tools like 'list_submittals' by emphasizing the project-scope and explicitly mentions pagination, filtering, and use cases (enumerating, finding IDs, filtering).

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 says 'Use this to enumerate Submittals when you need a paginated overview, to find IDs, or to filter by query parameters,' which provides clear context for when to use the tool. It does not explicitly exclude alternatives, but the sibling list includes other specific list tools, so the guidance is adequate.

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