Skip to main content
Glama
Sign In
Clipwright

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a personal actor

delete_actor
Destructive

Delete a personal actor while keeping existing videos. Deletion is refused when an unfinished run uses it; catalog actors cannot be deleted.

Instructions

Delete a personal actor; videos made with it stay. Refused while an unfinished run uses it; catalog actors are not deletable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actor_id": "<actor_id>"
    },
    "name": "delete_actor"
  }
}

Input Schema

NameRequiredDescriptionDefault
actor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.45.0
    • removedInput schema / properties / actor_id / description
      Removed value: -"Personal actor id from list_actors."
  2. Changed1 schema field changedv0.39.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. First observedv0.20.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond destructiveHint=true: outputs created with the actor survive the deletion, the call fails when a run is in flight, and the operation only applies to a subset of actors. These are exactly the side-effect and precondition facts an agent needs before invoking a destructive tool.

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?

Three tight clauses deliver the action, the retained artifact, and the two refusal conditions with no filler. Front-loaded with the verb and resource, and each clause earns its place.

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 single-parameter destructive tool with no output schema, the description covers effect, preconditions, and scope well. The remaining gap is procedural — how to discover a valid actor_id and whether the deletion can be undone — which is minor but not nothing for an irreversible operation.

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 0% and the only parameter, actor_id, is untyped beyond 'string, minLength 1' with no explanation in the description. The distinction between personal and catalog actors implicitly constrains which IDs are valid, but it does not say where to obtain an ID or what form it takes.

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 ('Delete a personal actor') and immediately narrows the scope to personal actors, distinguishing it from the catalog-actor tools that share the sibling list. An agent can tell exactly what is removed without opening the schema.

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?

Gives two concrete exclusions: it is refused while an unfinished run references the actor, and catalog actors cannot be deleted at all. It does not name an alternative tool (e.g. delete_creator_profile) or point to how to find eligible actor IDs, so the routing guidance is clear but not fully explicit.

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