SignNow MCP Server

Official

by signnow

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Create from template and embedded sending

create_embedded_sending_from_template

Create a document from a template and an embedded sending link for signing. Use for template or template group IDs.

Instructions

Create a document or document group from a template or template group, then create an embedded sending link immediately. This tool is ONLY for templates and template groups.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Optional name for the new document or document group
`type`	No	Type of sending step: 'manage', 'edit', or 'send-invite'	manage
`entity_id`	Yes	ID of the template or template group
`entity_type`	No	Type of entity: 'template' or 'template_group' (optional, auto-detected if not provided).
`redirect_uri`	No	Optional redirect URI after completion
`link_expiration`	No	Link expiration in minutes (15–45)
`redirect_target`	No	Optional redirect target

Output Schema

TableJSON Schema

Name	Required	Description
`sending_url`	Yes	URL for the embedded sending
`sending_entity`	Yes	Type of sending entity: 'document', 'document_group', or 'invite'
`created_entity_id`	Yes	ID of the created document or document group
`created_entity_name`	Yes	Name of the created entity
`created_entity_type`	Yes	Type of created entity: 'document' or 'document_group'

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.4.0May 27, 2026
Removedv2.2.3May 20, 2026

Changed8 schema fields changedv2.2.1May 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / entity_type / description

Previous value: -"Type of entity: 'template' or 'template_group' (optional). If you're passing it, make sure you know what type you have. If it's not found, try using a different type."New value: +"Type of entity: 'template' or 'template_group' (optional, auto-detected if not provided)."

changedInput schema / properties / link_expiration / anyOf

Previous value: -[
-  {
-    "maximum": 45,
-    "minimum": 14,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 45,
+    "minimum": 15,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / link_expiration / description

Previous value: -"Optional link expiration in days (14-45)"New value: +"Link expiration in minutes (15–45)"

changedInput schema / properties / redirect_target / description

Previous value: -"Optional redirect target: 'self' (default), 'blank'"New value: +"Optional redirect target"

changedInput schema / properties / type / default
```
Previous value: -nullNew value: +"manage"
```

removedOutput schema / properties / sending_id

Removed value: -{
-  "description": "ID of the created embedded sending",
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "created_entity_id",
-  "created_entity_type",
-  "created_entity_name",
-  "sending_id",
-  "sending_entity",
-  "sending_url"
-]New value: +[
+  "created_entity_id",
+  "created_entity_type",
+  "created_entity_name",
+  "sending_entity",
+  "sending_url"
+]

Changed14 schema fields changedv1.0.0Jan 3, 2026
- removedInput schema / properties / entity_id / title
```
Removed value: -"Entity Id"
```
- removedInput schema / properties / entity_type / title
```
Removed value: -"Entity Type"
```
- removedInput schema / properties / link_expiration / title
```
Removed value: -"Link Expiration"
```
- removedInput schema / properties / name / title
```
Removed value: -"Name"
```
- removedInput schema / properties / redirect_target / title
```
Removed value: -"Redirect Target"
```
- removedInput schema / properties / redirect_uri / title
```
Removed value: -"Redirect Uri"
```
- removedInput schema / properties / type / title
```
Removed value: -"Type"
```
- removedOutput schema / properties / created_entity_id / title
```
Removed value: -"Created Entity Id"
```
- removedOutput schema / properties / created_entity_name / title
```
Removed value: -"Created Entity Name"
```
- removedOutput schema / properties / created_entity_type / title
```
Removed value: -"Created Entity Type"
```
- removedOutput schema / properties / sending_entity / title
```
Removed value: -"Sending Entity"
```
- removedOutput schema / properties / sending_id / title
```
Removed value: -"Sending Id"
```
- removedOutput schema / properties / sending_url / title
```
Removed value: -"Sending Url"
```
- removedOutput schema / title
```
Removed value: -"CreateEmbeddedSendingFromTemplateResponse"
```
First observedOct 6, 2025

TDQS

A4.2/5.0

Behavior4/5

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

Discloses the creation and immediate link generation behavior, which aligns with annotations (readOnlyHint=false). It adds context beyond annotations but could mention potential side effects like link expiration.

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?

Two short sentences, no unnecessary words. Purpose and constraint are front-loaded.

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?

With 7 parameters, an output schema, and high schema coverage, the description covers the core goal. Minor missing context about the 'type' parameter's effect, but schema fills that gap.

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?

Schema coverage is 100%, so parameters are well-documented in the schema. The description does not add significant new information beyond what is in the 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?

The description clearly states it creates a document/group from a template/group and immediately creates an embedded sending link. The phrase 'ONLY for templates and template groups' distinguishes it from siblings like create_embedded_sending.

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?

Explicitly states the tool is only for templates and template groups, providing clear context. However, it does not explicitly contrast with alternatives like create_embedded_sending or create_from_template.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.