# send-for-signing

The send-for-signing MCP tool: send a generated document that is waiting for approval to the signers its template names, through DocuSign.

> Kind: Guide · Updated: Nov 4, 2026

Sends a document that is waiting for approval to the signers its template names, through DocuSign. It does the same as clicking Approve on the record page. The agent should confirm the signers with you before calling it, because the email to signers cannot be taken back. Calling it again for a document that was already sent sends nothing new and returns how signing stands.

## Before you use this tool

The user the connection acts as needs a CloudFiles Document Generation license. See Who the Agent Acts As. DocuSign must be connected to your CloudFiles account, and the document's template must name signers in its signing settings.

## Inputs

| Input | Required | Description |
|---|---|---|
| documentId | Yes | The documentId that generate-document returned. |

## Outputs

On the first call, send-for-signing answers as soon as the document is handed over for sending, with these fields.

| Field | Description |
|---|---|
| documentId | The document's ID. |
| status | ready, because only a saved document can be sent. |
| recordId | The Salesforce record the document was filled from. |
| fileName | The document's file name. |
| savedFileId | The saved file's ID in its library. On a Salesforce record, the ContentDocument ID. |
| savedLibrary | Where the document was saved: salesforce for the record's Salesforce Files, otherwise the folder's library. |
| savedDriveId | The drive the document was saved in, for libraries with drives. |
| previewUrl | Opens the document in the CloudFiles viewer. Stops working after a few minutes. |
| downloadUrl | Downloads the document. The link expires after a short time. |
| signingStatus | sending, because the document is on its way to DocuSign. |
| signers | Who the document is sent to, signers first in signing order and then those who receive a copy. Each has the status not_sent until DocuSign sends it. The signer fields are listed in get-document-status. |

A repeat call sends nothing new. It answers with how signing stands then: signingStatus moves on to sent, completed, declined, voided or failed, each signer shows their own status, error says why if signing failed, and the signed copy's links are added once signing is completed.

## When a document can be sent

The document must be ready and its signingStatus must be waiting. If the document is still being generated or prepared for signing, the tool asks the agent to check again with get-document-status. If the document failed, or its template names no signers, the tool says there is nothing to send. If DocuSign is not connected to your CloudFiles account, the tool says so and the document stays waiting.

## Example requests

| You ask | What the agent does |
|---|---|
| Looks good, send it for signing. | Shows you the signers from get-document-status, waits for your confirmation and then calls send-for-signing. |
| Generate the MSA and send it to the customer for signature. | Calls generate-document, then get-document-status until the document is waiting for approval, confirms the signers with you and calls send-for-signing. |