SignNow MCP Server

Official

Overview Schema Related Servers Score Discussions

Create embedded editor link

create_embedded_editor

Create an embedded editor to edit documents, document groups, templates, or template groups. Automatically creates a document from templates for editing.

Instructions

Create embedded editor for editing a document, document group, template, or template group. For templates and template groups, automatically creates a document/group first, then creates the embedded editor.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Optional name for the new document or document group (used only when entity_type is template or template_group)
`entity_id`	Yes	ID of the document, document group, template, or template group
`entity_type`	No	Type of entity: 'document', 'document_group', 'template', or 'template_group' (optional). Auto-detected if not provided.
`redirect_uri`	No	Optional redirect URI after completion
`redirect_target`	No	Optional redirect target: 'self' (default), 'blank'
`link_expiration_minutes`	No	Link lifetime in minutes (15–43200). Default: 15 min.

Output Schema

TableJSON Schema

Name	Required	Description
`editor_url`	Yes	URL for the embedded editor
`editor_entity`	Yes	Type of editor entity: 'document' or 'document_group'
`created_entity_id`	No	ID of the entity created from template (None when entity was document/document_group)
`created_entity_name`	No	Name of the entity created from template (None when entity was document/document_group)
`created_entity_type`	No	Type of created entity: 'document' or 'document_group' (None when entity was document/document_group)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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

Changed11 schema fields changedv2.2.1May 12, 2026

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

changedInput schema / properties / entity_id / description

Previous value: -"ID of the document or document group"New value: +"ID of the document, document group, template, or template group"

changedInput schema / properties / entity_type / anyOf

Previous value: -[
-  {
-    "enum": [
-      "document",
-      "document_group"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "document",
+      "document_group",
+      "template",
+      "template_group"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / entity_type / description

Previous value: -"Type of entity: 'document' or 'document_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: 'document', 'document_group', 'template', or 'template_group' (optional). Auto-detected if not provided."

removedInput schema / properties / link_expiration

Removed value: -{
-  "anyOf": [
-    {
-      "maximum": 43200,
-      "minimum": 15,
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Optional link expiration in minutes (15-43200)"
-}

addedInput schema / properties / link_expiration_minutes

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 43200,
+      "minimum": 15,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Link lifetime in minutes (15–43200). Default: 15 min."
+}

addedInput schema / properties / name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional name for the new document or document group (used only when entity_type is template or template_group)"
+}

changedOutput schema / description

Previous value: -"Response model for creating embedded editor."New value: +"Response model for creating embedded editor.\n\nWhen the editor is created for a template-originated entity, the created_entity_*\nfields are populated. For direct document/document_group calls they are None."

addedOutput schema / properties / created_entity_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ID of the entity created from template (None when entity was document/document_group)"
+}

addedOutput schema / properties / created_entity_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Name of the entity created from template (None when entity was document/document_group)"
+}

addedOutput schema / properties / created_entity_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Type of created entity: 'document' or 'document_group' (None when entity was document/document_group)"
+}

Changed8 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 / redirect_target / title
```
Removed value: -"Redirect Target"
```
- removedInput schema / properties / redirect_uri / title
```
Removed value: -"Redirect Uri"
```
- removedOutput schema / properties / editor_entity / title
```
Removed value: -"Editor Entity"
```
- removedOutput schema / properties / editor_url / title
```
Removed value: -"Editor Url"
```
- removedOutput schema / title
```
Removed value: -"CreateEmbeddedEditorResponse"
```
First observedOct 6, 2025

TDQS

A3.8/5.0

Behavior4/5

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

Description adds important behavioral context beyond annotations: the auto-creation of documents/groups when using templates or template groups. Annotations indicate readOnlyHint=false and destructiveHint=false, which align with the create operation. No contradictions.

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 sentences, front-loaded with purpose, no redundant information. Every sentence is informative and concise.

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 core functionality and special behavior for templates. Given an output schema exists for return values, the description is mostly complete. Could mention prerequisites or error handling but not required for a clear tool understanding.

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 provides 100% coverage for all 6 parameters. The description adds minimal extra meaning beyond the schema, only explaining that the 'name' parameter is used when entity_type is template. Baseline 3 is appropriate.

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?

Clearly states the tool creates an embedded editor for editing documents, document groups, templates, or template groups. Also explains the distinct behavior for templates (auto-creates a document first), which differentiates from sibling tools like create_embedded_editor_from_template.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., create_embedded_editor_from_template, create_embedded_invite). The description does not mention when-not-to-use or provide context for tool selection.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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