Skip to main content
Glama

Create embedded signing invite

create_embedded_invite
Destructive

Creates an embedded invite for signing documents or templates, automatically generating a document when using a template.

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.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_group_invite_idNoID of the created document group embedded invite; populated only when invite_entity is 'document_group', otherwise None
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_typeNoType of created entity: 'document' or 'document_group' (None when entity was document/document_group)
created_entity_nameNoName of the entity created from template (None when entity was document/document_group)
Behavior3/5

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

The description reveals the automatic creation of a document/group for templates, which is a key side effect. However, it does not elaborate on other behavioral aspects such as destructive actions (despite destructiveHint=true), authentication requirements, or rate limits. The annotations already indicate destructiveHint=true, but the description adds only the creation side effect.

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 concise sentences that front-load the main purpose and add a critical behavioral detail. No wasted words.

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, anyOf schemas, output schema exists), the description covers the core behavior and the auto-creation nuance. It does not mention that orders can be a JSON string or potential errors, but the output schema and high schema coverage compensate. A small gap in not discussing usage prerequisites.

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 description coverage is 100%, so the schema already documents each parameter well. The description adds a small nuance about automatic creation for templates, but does not provide additional meaning beyond what the schema offers. Baseline of 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 the tool creates an embedded invite for signing, and specifies the supported entity types (document, document group, template, template group). It also distinguishes a special behavior for templates, which helps differentiate from siblings like 'create_embedded_invite_from_template' or 'send_invite'.

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

Usage Guidelines3/5

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

The description implies usage for embedded signing flows but does not explicitly compare with alternatives or state when to use this tool versus siblings like 'send_invite' or 'create_embedded_invite_from_template'. No exclusion criteria or context are provided.

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