Easy Scribe

Create a document from a recording

create_document

Turns a screen recording into documentation: Easy Scribe writes numbered steps with a screenshot at each one, from what happens on screen and any narration, so recordings without audio work too. Takes video_url (a direct link to an .mp4, .webm or .mov file) or upload_path (from create_upload_url). Each call creates a new document in the user's Easy Scribe account, which counts toward the Free plan's monthly allowance; processing takes a few minutes, and get_document reports progress and returns the finished document. When the allowance is used up, it returns an error that says when more documents are available.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_document"
  }
}

Input Schema

Name	Required	Description
`title`	No	Document title, for example "How to issue a refund".
`language`	No	Language to write in, for example English. Default Auto (the language spoken in the video).
`template`	No	Document format. Default general. See list_templates.
`video_url`	No	Direct https link to a video file. Page links (Loom, YouTube) open a web page rather than a video file; such videos are downloaded first and uploaded with create_upload_url.
`redact_pii`	No	Blur personal data in text and screenshots. Requires Easy Scribe Pro.
`description`	No	Optional: the audience, purpose or focus the user asked for. Easy Scribe sees the video itself, so this doesn't need to describe what happens in it.
`upload_path`	No	The upload_path returned by create_upload_url.
`workspace_id`	No	Optional workspace from list_workspaces. Default: personal workspace.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / description / description

Previous value: -"Optional: the audience, purpose or focus the user asked for. Easy Scribe sees the video itself, so don't describe what happens in it."New value: +"Optional: the audience, purpose or focus the user asked for. Easy Scribe sees the video itself, so this doesn't need to describe what happens in it."

changedInput schema / properties / video_url / description

Previous value: -"Direct https link to a video file. Page links (Loom, YouTube) do not work; download the file and use create_upload_url."New value: +"Direct https link to a video file. Page links (Loom, YouTube) open a web page rather than a video file; such videos are downloaded first and uploaded with create_upload_url."

Changed1 schema field changedNov 9, 2026
- removedInput schema / required
```
Removed value: -[
-  "title"
-]
```
First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare that this is a non-read-only, non-idempotent, open-world write; the description adds the details that matter: every call creates a new document and consumes Free-plan allowance, processing is asynchronous and takes minutes, and exhaustion produces a specific error. Those quota, latency, and failure behaviors are exactly what an agent needs before repeated invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, and the remainder is dense but relevant. Some sentences are long and pack multiple ideas (quota plus async plus error), which slightly hurts scannability but wastes little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight parameters, no output schema, and an asynchronous workload, the definition covers the full lifecycle: inputs, media constraints, quota consumption, multi-minute processing, polling via get_document, and the allowance-exhausted error. Nothing essential to invoking it correctly is missing.

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%, so each parameter is already documented in the schema, including the video_url versus upload_path distinction and the template list. The description restates the accepted file types and confirms audio-less recordings work, which is marginal added value over the schema rather than new meaning.

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 opens with a specific verb and resource: turning a screen recording into numbered-step documentation with screenshots. It also distinguishes itself from siblings by naming create_upload_url for page links and get_document for progress tracking.

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?

It gives clear selection guidance between the two input routes (video_url for direct file links, upload_path for page links already downloaded via create_upload_url) and points to get_document for polling. It stops short of explicit when-not-to-use conditions, such as when to use list_documents or share_document instead.

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

All Easy Scribe tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.