Skip to main content
Glama
signnow

SignNow MCP Server

Official
by signnow
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Create from template and embedded editor

create_embedded_editor_from_template

Create a document from a template and generate an embedded editor link for immediate editing.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional name for the new document or document group
entity_idYesID of the template or template group
entity_typeNoType of entity: 'template' or 'template_group' (optional, auto-detected if not provided).
redirect_uriNoOptional redirect URI after completion
link_expirationNoLink expiration in minutes (15–45)
redirect_targetNoOptional redirect target

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
editor_urlYesURL for the embedded editor
editor_entityYesType of editor entity: 'document' or 'document_group'
created_entity_idYesID of the created document or document group
created_entity_nameYesName of the created entity
created_entity_typeYesType of created entity: 'document' or 'document_group'

Schema Changelog

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

  1. Addedv2.4.0
  2. Removedv2.2.3
  3. Changed8 schema fields changedv2.2.1
    • 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": 43200,
-    "minimum": 15,
-    "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 minutes (15-43200)"New value: +"Link expiration in minutes (15–45)"
    • changedInput schema / properties / name / description
      Previous value: -"Name for the new document or document group"New value: +"Optional name for the new document or document group"
    • changedInput schema / properties / redirect_target / description
      Previous value: -"Optional redirect target: 'self' (default), 'blank'"New value: +"Optional redirect target"
    • removedOutput schema / properties / editor_id
      Removed value: -{
-  "description": "ID of the created embedded editor",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "created_entity_id",
-  "created_entity_type",
-  "created_entity_name",
-  "editor_id",
-  "editor_entity",
-  "editor_url"
-]New value: +[
+  "created_entity_id",
+  "created_entity_type",
+  "created_entity_name",
+  "editor_entity",
+  "editor_url"
+]
  4. Changed13 schema fields changedv1.0.0
    • 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"
    • 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 / editor_entity / title
      Removed value: -"Editor Entity"
    • removedOutput schema / properties / editor_id / title
      Removed value: -"Editor Id"
    • removedOutput schema / properties / editor_url / title
      Removed value: -"Editor Url"
    • removedOutput schema / title
      Removed value: -"CreateEmbeddedEditorFromTemplateResponse"
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructiveness. Description adds 'immediately' for link creation but lacks details on side effects like template consumption or account impact. Adequate given annotations.

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, no wasted words, front-loaded with core action. Perfectly 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 purpose and scope well; output schema handles return info. Could mention error conditions or prerequisites, but sufficient for an agent with schema and annotations.

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% and descriptions are clear. The description adds no additional meaning beyond what's in the schema, so 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?

The description clearly states it creates a document/group and an embedded editor link from a template/group, with explicit 'ONLY for templates and template groups' distinguishing it from siblings like create_embedded_editor.

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 tool is only for templates/template groups, giving clear context. Does not explicitly compare to alternatives like create_embedded_editor or create_from_template, but the 'ONLY' implies exclusion.

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