Easy Scribe

Upload a recording

create_upload_url

Uploads a screen recording to Easy Scribe, which turns it into documentation: a step-by-step guide, SOP, tutorial or user guide with screenshots. Use it when the user wants a document from a video they have; it works before they have named or picked the file. In apps that show MCP Apps (Claude, ChatGPT), an upload box appears with the result, and the box creates the document when the upload finishes. Files attached to a chat can't be passed to Easy Scribe, so the user chooses the video in the box. Title, template, language and description are optional. Elsewhere the result has an upload link and a command; how_to_upload explains them. For a public video link, use create_document with video_url.

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_upload_url"
  }
}

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.
`file_name`	No	The video's file name if you know it, for example onboarding-walkthrough.mp4. Optional.
`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.
`workspace_id`	No	Optional workspace from list_workspaces. Default: personal workspace.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field 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."

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / file_name / description

Previous value: -"The video's file name, for example onboarding-walkthrough.mp4."New value: +"The video's file name if you know it, for example onboarding-walkthrough.mp4. Optional."

removedInput schema / required
```
Removed value: -[
-  "file_name"
-]
```

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by describing two distinct execution environments: in MCP Apps hosts an upload box appears and creates the document when the upload finishes, elsewhere the result is an upload link plus a command explained by how_to_upload. It also discloses a real constraint that chat-attached files cannot be passed to Easy Scribe, which is exactly the kind of behavioral detail an agent would otherwise get wrong.

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?

Front-loaded with the action and outcome, then the host-specific behavior, then the sibling redirect, which is a sensible order. The sentence listing which fields are optional is largely redundant given all seven parameters are optional and fully described in the schema, so a small amount of text does not earn its place.

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?

For a no-required-parameter upload tool with no output schema, the description covers the trigger, both host behaviors, the return shape in each case, the attached-file limitation, and the correct alternative for public links. Nothing an agent needs in order to call it correctly or route away from it 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 description coverage is 100%, so every parameter is already documented, and the description only restates optionality ("Title, template, language and description are optional") without adding format or interaction detail. The one genuinely useful hint, that the tool works before the file is named or picked, is about flow rather than parameter meaning. Baseline 3 applies.

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?

States a specific verb and resource ("Uploads a screen recording to Easy Scribe") plus the transformation outcome (step-by-step guide, SOP, tutorial, user guide with screenshots). It also differentiates itself from siblings by naming create_document for public video links and how_to_upload for the link/command flow.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("Use it when the user wants a document from a video they have") and a key precondition ("works before they have named or picked the file"). It also names the alternative for a different case: "For a public video link, use create_document with video_url."

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.