Skip to main content
Glama
Sign In
clipy-recorder

@clipy/mcp

by clipy-recorder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_recording

DestructiveIdempotent

Rename a Clipy screen recording, rewrite its description, or set the expected result; pass null to clear description or expected result. Requires recordings:write permission.

Instructions

Rename a recording, rewrite its description, or set what the recorder expected to happen (expectedResult). Renaming also stops Clipy's auto-titling from overwriting the name later. Pass description or expectedResult as null to clear it. Needs a key with recordings:write.

Input Schema

NameRequiredDescriptionDefault
idYesThe recording's public id (the slug in its share URL, e.g. 'a1b2c3d4e5f6') or the full https://clipy.online/video/<id> URL.
nameNoThe new title. Omit to leave the title alone.
descriptionNoThe new description, or null to clear it.
expectedResultNoWhat the recorder expected to happen, or null to clear it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.18.0
    • addedInput schema / properties / expectedResult
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 1000,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "What the recorder expected to happen, or null to clear it."
+}
  2. Addedv0.17.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare mutation, destructiveness, idempotency, and open-world behavior. The description adds useful context beyond that: renaming disables Clipy's auto-titling, description and expectedResult can be cleared with null, and a recordings:write key is required.

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 four concise sentences with the main operations front-loaded. Each sentence adds practical information about effects, clearing behavior, or authorization without filler.

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?

For a mutation tool with full schema coverage and detailed annotations, the description covers the essential behavioral context: write scope, null-clearing semantics, and the auto-titling side effect. It could mention what the tool returns, but no output schema exists and the description is otherwise sufficient.

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 the input schema already documents id, name, description, and expectedResult. The description reinforces the null-clearing behavior but adds little semantic detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs and resources: renaming, rewriting the description, and setting expectedResult on a recording. It clearly tells an agent what the tool does, but it does not differentiate this from sibling tools such as edit_recording or organize_recording.

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 by listing the mutable fields and the recordings:write prerequisite, but it gives no explicit guidance on when to choose this tool over edit_recording or other recording-management siblings. The null-clearing note helps, but alternatives and exclusions are absent.

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

Deploy Server

Other Tools