Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Submittal

create_submittal

Create a new Submittal in a Procore project. Requires project ID and submittal number.

Instructions

Create a new Submittal associated with the specified Project. Use this to create a new Submittals in Procore. Creates a new Submittals and returns the created object on success (HTTP 201). Required parameters: project_id, number. Procore API (v1.1): Project Management > Submittals. Endpoint: POST /rest/v1.1/projects/{project_id}/submittals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
send_emailsNoQuery string parameter — designates whether or not emails will be sent (default false)
actual_delivery_dateNoJSON request body field — the Actual Delivery Date of the Submittal *This field can only be set if the project has submittal delivery information enabled
attachmentsNoJSON request body field — submittal attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files.
confirmed_delivery_dateNoJSON request body field — the Confirmed Delivery Date of the Submittal *This field can only be set if the project has submittal delivery information enabled
cost_code_idNoJSON request body field — the ID of the Cost Code of the Submittal *This field can only be set by admins
custom_textarea_1NoJSON request body field — *This field can only be set by admins
custom_textfield_1NoJSON request body field — *This field can only be set by admins
descriptionNoJSON request body field — the Description of the Submittal
design_team_review_timeNoJSON request body field — the Design Team Review Time of the Submittal (in days) *This field can only be set if the project has schedule calculations enabled
distribution_member_idsNoJSON request body field — the IDs of the Distribution Members of the Submittal
due_dateNoJSON request body field — the Due Date of the Submittal *This field is not available to be set if sequential approvers is enabled
internal_review_timeNoJSON request body field — the Internal Review Time of the Submtital (in days) *This field can only be set if the project has schedule calculations enabled
issue_dateNoJSON request body field — the Issue Date of the Submittal *This field can only be set by admins
lead_timeNoJSON request body field — the Lead Time of the Submittal (in days) *This field can only be set by admins or if the project has schedule calculations enabled
location_idNoJSON request body field — the Location of the Submittal
numberYesJSON request body field — the Number of the Submittal
privateNoJSON request body field — whether the Submittal is Private or not
prostore_file_idsNoJSON request body field — an array of Prostore File IDs. The Prostore Files will be associated with the Submittal as attachments.
received_dateNoJSON request body field — the Received Date of the Submittal *This field can only be set by admins
received_from_idNoJSON request body field — the Received From of the Submittal
required_on_site_dateNoJSON request body field — the Required On Site Date of the Submittal *This field can only be set by admins or if the project has schedule calculations enabled
responsible_contractor_idNoJSON request body field — the Responsible Contractor of the Submittal
revisionNoJSON request body field — the Revision of the Submittal
scheduled_task_keyNoJSON request body field — the key of the Scheduled Task of the Submittal. Note that use of this parameter is deprecated. Please use `scheduled_task_id` instead. *This field can only be set if the project has submittal deliv...
scheduled_task_idNoJSON request body field — the ID of the Scheduled Task of the Submittal *This field can only be set if the project has submittal delivery information enabled and the user has permissions to view the calendar tool
source_submittal_log_idNoJSON request body field — the ID of the Source Submittal. *By setting this field, the submittal will be created as a revision of source submittal.
specification_section_idNoJSON request body field — the ID of the Specification Section of the Submittal
status_idNoJSON request body field — the ID of the Submittal Status of the Submittal *This field can only be set by admins
sub_job_idNoJSON request body field — the ID of the Sub Job of the Submittal
submit_byNoJSON request body field — the Submit By Date of the Submittal *This field can only be set by admins
Behavior3/5

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds that a successful creation returns HTTP 201 and the created object, and specifies the API version. However, it does not mention permissions, rate limits, or side effects like email notifications, which would be valuable beyond the annotations.

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 concise, front-loads the purpose, and contains no redundant information. Every sentence adds value: purpose, usage, required params, and endpoint details.

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?

The description covers the core purpose and required parameters. With full schema descriptions for all params, it is mostly complete. However, it does not explain return structure beyond 'returns the created object', nor does it address multipart upload nuances for attachments, which are in the schema.

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 schema already documents all 31 parameters. The description only highlights required fields (project_id, number) already in the schema. It adds no additional meaning beyond what is in the schema.

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 the tool creates a new Submittal associated with a project, specifies the required parameters (project_id, number), and identifies the endpoint. It is distinct from sibling tools like create_submittal_response or update_submittal.

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 indicates when to use the tool ('Use this to create a new Submittals') but provides no explicit guidance on when not to use it or alternatives among the many sibling create tools. It does mention required parameters, but lacks contextual exclusions.

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