Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Submittal Approver

update_submittal_approver
Idempotent

Update a submittal approver's response, comments, dates, or attachments in Procore. Send only changed fields, providing approver, project, submittal, and response IDs.

Instructions

Update Submittal Approver for the specified Submittal. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "submittal_approver" in the request payload for you. id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified submittal approver on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. 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
commentNoJSON request body field — the comment for this Submittals operation
sent_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
project_idYesQuery string parameter — unique identifier for the project.
upload_idsNoJSON request body field — uploads to attach to the response
send_emailsNoQuery string parameter — designates whether or not emails will be sent (default false)
submittal_idYesQuery string parameter — unique identifier of the submittal
returned_dateNoJSON request body field — parameter is only available to admins.
attachment_idsNoJSON request body field — submittal Approver's Attachment IDs. The Attachments specified here will be saved as attachments through the request.
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...
submittal_response_idYesJSON request body field — submittal_response_id
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.
Behavior5/5

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

The description discloses partial-update semantics, the automatic nesting of fields under 'submittal_approver', the return of the modified object, and common error HTTP statuses (401/403/404). These go well beyond the annotations, which only state read-only=false, idempotent=true, and destructive=false. No contradictions with 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 a compact paragraph with every sentence earning its place: purpose, partial-update behavior, field mapping, id resolution, return value, error handling, required params, and API reference. It is front-loaded with the core purpose and avoids redundancy.

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

Completeness5/5

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

Despite having 13 parameters and no output schema, the description covers the key behaviors an agent needs: successful return value, error semantics, id resolution, partial updates, and required parameters. The schema descriptions handle individual parameter details, so the description is complete for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful context by explaining that record fields should be passed as top-level arguments and will be automatically nested under 'submittal_approver' in the payload—information not present in the schema. This helps the agent avoid incorrect payload construction.

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 opens with a specific verb+resource: 'Update Submittal Approver for the specified Submittal.' It clearly distinguishes from sibling tools like update_submittal or update_submittal_response by targeting the submittal approver specifically. The endpoint and API section further reinforce the unambiguous purpose.

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 context: it is a partial update tool ('send only the fields you intend to change'), advises resolving the id with the matching list tool first, and lists required parameters. It does not explicitly state when not to use this tool or name alternatives, so it stops short of the top score.

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