Youtrust

Add an approver (approves a DRAFT before signers sign, NOT a signer), from scratch (first_name, last_name, email). Returns the created approver `approver_id`, `status`, `recipient_stage_index`, identity fields and `custom_text`. Ordering needs custom recipient order or approver reordering enabled, else it errors. One approver per call; chain via a returned `approver_id` as next `insertAfterId`. Drafts only. Adding from an existing user/contact/signer needs the Youtrust app. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

add-signature-request-approver

Add ONE follower ("CC" recipient) to a signature request. Followers never sign: they track the request and receive its emails. On a draft they are notified once it is sent; on a sent request, immediately. Returns the created follower. One follower per call. A canceled or declined request, an email already following it, or an exceeded follower quota is rejected with an explicit message: surface it verbatim, do not retry. Followers cannot be edited: to change one's email or locale, call remove-signature-request-follower with its `follower_id`, then add the new one here. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

add-signature-request-follower

Add ONE ad-hoc signer (from scratch: name + email, not linked to a contact or user) to an editable signature request (draft or paused only). No signature fields are placed for the new signer: the user MUST position their fields in the Youtrust app (request url) before sending. Returns the created signer and its attributes. Do NOT propose adding or editing documents or fields: those happen in the Youtrust app. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

add-signature-request-signer

Create a signature request DRAFT from scratch, WITHOUT a template. NEVER sends. USE THIS BY DEFAULT when the user named no template. The user then adds documents and recipients in the Youtrust app from the returned `url`: expected, not a limitation, never fall back to a template to avoid it. ALWAYS tell the user the `workspace_name` used and the `custom_experience` applied. Pass only the settings the user asked for; the others keep the organization defaults. Later changes: update-signature-request. Do NOT offer (Youtrust app only): cancelling, deleting or duplicating the draft. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

create-signature-request

Create a signature request DRAFT from an EXISTING template the user asked for. NEVER sends. If the user named no template, use create-signature-request instead: never pick or offer a template on their behalf. Returns the draft with its assigned `placeholder_signers`, `recurring_signers` (fixed in the template, info only), resolved `read_only_text_fields` and a `url` to review it before confirmation. Afterwards only add-signature-request-signer and send-signature-request may follow. Do NOT offer (Youtrust app only): removing or editing signers, document or field changes, cancel, delete, duplicate. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

create-signature-request-from-template

Full detail of ONE signature request by UUID: settings (status, delivery mode, recipient ordering, expiration, reminders, decline-to-sign, custom experience), workspace, sender, signers in signing order (status, signed_at) and approvers, each with custom_text and recipient_stage_index, followers, documents, labels, decline/rejection info and the app `url`. History: get-signature-request-activity-feed. Never returns signing, approval or follower links. Read-only. Do NOT offer (Youtrust app only): reminders, edit, cancel, archive, delete, duplicate, resend, extend, recipients, documents, fields. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

get-signature-request

Read the chronological activity feed (history) of one signature request: creation, sending, signatures, declines, cancellations, expirations, reminders, approver decisions, identity verifications, document renames. Newest first; `event_type` discriminates the shape of `data`. Current state: get-signature-request. Read-only. Do NOT offer (Youtrust app only), even when the feed shows such events: reminders, editing, canceling, archiving, deleting, duplicating, resending or extending the request, managing signers or fields. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

get-signature-request-activity-feed

Fetch one approver (approves before signers sign, NOT a signer) of a signature request. Returns the approver `approver_id`, identity fields, `status`, `approved_at`, `custom_text`, and its `recipient_stage_index` in the flow. Use `approver_id` as `insertAfterId` for add-signature-request-approver or as `approverId` for remove-signature-request-approver. Approver groups (deferred identities) are NOT supported: their ids come back as not found; check the Youtrust app. Read-only. To edit an approver, use update-signature-request-approver; to send reminders, use the Youtrust app. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

get-signature-request-approver

Fetch ONE signer of a signature request by its id: `status`, name, `email`, `phone_number`, `locale`, `signature_level`, `authentication_mode`, `delivery_mode`, `custom_text`, `recipient_stage_index` (1-based signing order) and `signed_at` (null until signed). Use it to read a signer's current values before update-signature-request-signer, or to check whether they were notified (`status` other than `initiated`). Read-only: modifies nothing, notifies no one. Signers only: approvers are read with get-signature-request-approver. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

get-signature-request-signer

List the custom experiences (brandings) the user can apply to a signature request. Each result gives `custom_experience_id` (the `customExperienceId` to pass to create-signature-request or update-signature-request), `name`, and `is_default` (the one applied when `customExperienceId` is omitted). Paginated: the organization default first, then newest first. There is no search parameter: page through the list and match the name the user gave; if several match, ask. Do NOT offer (Youtrust app only): creating, editing or deleting a custom experience. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature". Include telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message. Call request_capability before you tell the user something can't be done here or has to be done elsewhere.

list-custom-experiences