Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Submittals

list_submittals
Read-onlyIdempotent

Retrieve a paginated list of submittals filtered by project ID and various criteria such as status, location, or date range.

Instructions

This is a deprecated endpoint. Please use /submittals endpoint. See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. 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: Project Management > Submittals. Endpoint: GET /rest/v1.0/submittal_logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
filters__approved_idNoQuery string parameter — filters[approved_id]
filters__ball_in_courtNoQuery string parameter — filters[ball_in_court]
filters__date_rangeNoQuery string parameter — filter results by date range
filters__due_byNoQuery string parameter — filter results by due by
filters__end_dateNoQuery string parameter — filter results by end date
filters__include_sublocationsNoQuery string parameter — use together with `filters[location_id]`
filters__location_idNoQuery string parameter — location ID. Returns item(s) with the specified Location ID or a range of Location IDs.
filters__only_current_revisionNoQuery string parameter — filters[only_current_revision]
filters__queryNoQuery string parameter — return item(s) containing search query
filters__received_from_idNoQuery string parameter — filter results by received from id
filters__responseNoQuery string parameter — filter results by response
filters__responsible_contractor_idNoQuery string parameter — array of Responsible Contractor IDs. A single Responsible Contractor ID is also accepted.
filters__spec_divisionNoQuery string parameter — filters[spec_division]
filters__spec_section_idNoQuery string parameter — filters[spec_section_id]
filters__start_dateNoQuery string parameter — filter results by start date
filters__statusNoQuery string parameter — returns item(s) matching the specified status value.
filters__submittal_typeNoQuery string parameter — filters[submittal_type]
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.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior4/5

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

The description adds value beyond annotations by noting deprecation, pagination details (page/per_page, pagination metadata), required project_id, and linking to filtering documentation. It is consistent with annotations (readOnlyHint, idempotentHint). 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.

Conciseness4/5

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

The description is a single paragraph, efficiently front-loading deprecation and usage. It contains necessary details like pagination, required param, and API reference. Each sentence adds value, though it could be slightly more concise by omitting redundant phrases like 'See [Filtering on List Actions]...' but that is useful.

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

Completeness3/5

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

Given 21 parameters and no output schema, the description covers the basic purpose, deprecation, pagination, and required param. It lacks details on error conditions, rate limits, or return value structure beyond 'paginated JSON array.' The link to filtering docs helps, but overall it is adequate but not fully comprehensive for the high parameter count.

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 and required project_id but does not add meaning for the 18 other filter parameters. However, it provides a link for filtering capabilities, which aids understanding of the many filters. No contradiction or misleading info.

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 it enumerates Submittals for paginated overview, finding IDs, and filtering. It explicitly mentions it is a deprecated endpoint and specifies the endpoint path, distinguishing it from the newer /submittals endpoint.

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?

It gives clear guidance to use the /submittals endpoint instead because this is deprecated. It also states when to use this tool (paginated overview, find IDs, filter). Although it does not differentiate among sibling tools by name, the deprecation warning is a strong usage guideline.

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