Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Submittal Approver

update_submittal_approver

Modify a submittal approver's comment, response, attachments, or dates for a specific submittal. Only provided fields are updated.

Instructions

Update Submittal Approver for the specified Submittal. Use this to update an existing Submittals (only the supplied fields are changed). Updates the specified Submittals and returns the modified object on success. Required parameters: id, project_id, submittal_id, submittal_response_id. Procore API: Project Management > Submittals. Endpoint: PATCH /rest/v1.0/submittal_approvers/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — submittal Approver ID
project_idYesQuery string parameter — unique identifier for the project.
send_emailsNoQuery string parameter — designates whether or not emails will be sent (default false)
submittal_idYesQuery string parameter — unique identifier of the submittal
attachments_to_uploadNoJSON request body field — submittal Approver's 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_t...
attachment_idsNoJSON request body field — submittal Approver's Attachment IDs. The Attachments specified here will be saved as attachments through the request.
upload_idsNoJSON request body field — uploads to attach to the response
commentNoJSON request body field — the comment for this Submittals operation
submittal_response_idYesJSON request body field — submittal_response_id
sent_dateNoJSON request body field — parameter is only available to admins.
returned_dateNoJSON request body field — parameter is only available to admins.
forward_toNoJSON request body field — params used only when forwarding for review. Designates who the new reviewer is and what their due date is
associated_attachmentsNoJSON request body field — submital Approver's Attachments to be carried forward. The Attachments specified here will be carried forward to the next person in the workflow.
Behavior4/5

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

The description adds behavioral context beyond annotations: it specifies that only supplied fields are changed and that the modified object is returned on success. Annotations indicate a write operation (readOnlyHint=false) but no destructiveness, which is consistent.

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 (two sentences plus list of required params and API info) with no unnecessary words. It is front-loaded with the purpose and includes essential details efficiently.

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 13 parameters and no output schema, the description is reasonably complete. It covers purpose, usage, required parameters, and API source. It explains the return behavior (modified object) and partial update, which is sufficient for a mutation tool with high schema coverage.

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?

Input schema has 100% description coverage, so baseline is 3. The description lists required parameters but does not add significant meaning beyond the schema. It reinforces which parameters are mandatory but adds no new semantic detail.

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 'Update Submittal Approver for the specified Submittal' using a specific verb and resource. It distinguishes itself from sibling tools like 'update_submittal' by explicitly naming the target resource as 'Submittal Approver'.

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 provides clear usage context: it updates an existing submittal approver with only supplied fields changed (partial update). It lists required parameters. However, it does not explicitly mention when not to use it or provide alternatives.

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