Skip to main content
Glama

Replace invite recipient

update_invite_recipient
Destructive

Replace the current signer on a pending field invite with a new email address, automatically updating the invite and resending it. Supports documents and document groups.

Instructions

Replace the signing recipient on a pending field invite for a document or document group. Finds the pending invite for the current signer and replaces it with a new signer. For documents: deletes the old invite, creates a replacement, and triggers sending. For document groups: updates the pending step(s) with the new signer information. Only field invites are supported — freeform and embedded invites cannot be updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idYesID of the document or document group
current_emailYesEmail address of the current signer to replace
new_emailYesEmail address of the new signer
entity_typeNoType of entity: 'document' or 'document_group' (optional). Auto-detected if not provided (tries document_group first). Pass explicitly to save one API call.
roleNoRole name to match (for multi-role documents). If omitted, matches any role.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idYesDocument or document group ID
entity_typeYesEntity type: 'document' or 'document_group'
statusYesResult status: 'replaced' (invite recipient was replaced and resent), 'no_pending_invite' (no pending/created invite found for current_email), 'unsupported_invite_type' (freeform or embedded invites cannot be updated)
new_invite_idNoID of the newly created invite (populated only when status is 'replaced')
previous_emailYesEmail address of the replaced signer
new_emailYesEmail address of the new signer
updated_stepsNoList of step IDs that were updated (populated only for document_group with status 'replaced')
Behavior4/5

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

Beyond destructiveHint annotation, description details behavior: deletes old invite, creates replacement, triggers sending for documents; updates steps for document groups. No contradiction 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is two paragraphs, concise and front-loaded with key action. Each sentence adds value, though could be slightly trimmed.

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?

Covers different behaviors for documents vs document groups, auto-detection logic, and unsupported invite types. Output schema exists, so return values are handled. Adequate for a modification tool.

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. Description adds context about auto-detection of entity_type and role matching but does not significantly elaborate on parameter meaning beyond 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?

Description clearly states action 'Replace the signing recipient' and specifies resource 'pending field invite'. It distinguishes from siblings by noting that only field invites are supported, not freeform or embedded.

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?

States when to use: to replace a signer on a pending field invite. Explicitly excludes freeform/embedded invites. Does not compare directly with other tools like cancel_invite, but provides enough context for appropriate use.

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/signnow/sn-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server