Skip to main content
Glama

Create embedded signing invite

create_embedded_invite
Destructive

Create embedded signing invites for documents or templates. Automatically generates a document from a template before creating the invite with customized recipient orders.

Instructions

Create embedded invite for signing a document, document group, template, or template group. For templates and template groups, automatically creates a document/group first, then creates the embedded invite. The entity's state may have changed in the SignNow editor since you last looked — re-read the current state first and build this request from the current roles/fields, not from earlier in the conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional name for the new document or document group (used only when entity_type is template or template_group)
ordersYesList of orders with recipients (or a JSON string of the same).
entity_idYesID of the document, document group, template, or template group
entity_typeNoType of entity: 'document', 'document_group', 'template', or 'template_group' (optional). Auto-detected if not provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
invite_entityYesType of invite entity: 'document' or 'document_group'
recipient_linksYesArray of objects with role, invite id (for document invite) and link for recipients with delivery_type='link'
created_entity_idNoID of the entity created from template (None when entity was document/document_group)
created_entity_nameNoName of the entity created from template (None when entity was document/document_group)
created_entity_typeNoType of created entity: 'document' or 'document_group' (None when entity was document/document_group)
document_group_invite_idNoID of the created document group embedded invite; populated only when invite_entity is 'document_group', otherwise None
Behavior5/5

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

The description adds significant context beyond annotations: it discloses that for templates and template groups, it automatically creates a document/group first. The warning about stale state is also valuable. Annotations already indicate destructive and non-idempotent behavior, and the description aligns perfectly without contradiction.

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?

The description is two sentences with no unnecessary words. It front-loads the core purpose and follows with a critical caution. Every sentence earns its place.

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?

Given the tool's complexity (4 parameters, multiple entity types, output schema exists), the description covers the essential behaviors and adds a state-reading warning. It does not explain error conditions or the output format, but the output schema presumably handles that. Slightly incomplete for a full picture, but adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining that the 'name' parameter is only used when entity_type is template or template_group, and that 'entity_type' is auto-detected if not provided. This clarifies parameter usage beyond the schema descriptions.

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 the tool creates an embedded invite for signing, and specifies the supported entity types (document, document group, template, template group). It distinguishes from siblings by mentioning the auto-creation behavior for templates, which is unique to this tool.

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?

The description provides a crucial guideline: re-read the current state before building the request to avoid using stale roles/fields. However, it does not explicitly state when not to use this tool or directly compare with siblings like create_embedded_invite_from_template.

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