Skip to main content
Glama

Create embedded editor link

create_embedded_editor

Create an embedded editor for documents, document groups, templates, or template groups. Automatically generates a document from templates before opening the editor.

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
NameRequiredDescriptionDefault
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.
nameNoOptional name for the new document or document group (used only when entity_type is template or template_group)
redirect_uriNoOptional redirect URI after completion
redirect_targetNoOptional redirect target: 'self' (default), 'blank'
link_expiration_minutesNoLink lifetime in minutes (15–43200). Default: 15 min.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
editor_entityYesType of editor entity: 'document' or 'document_group'
editor_urlYesURL for the embedded editor
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)
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.

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