Skip to main content
Glama
Sign In
Clipwright

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List actors

list_actors
Read-only

Lists saved actors and their IDs, gender, age, and verified formats to help you select an actor_id for video ads; previews appear as markdown images, and personal actors can expire.

Instructions

Saved actors with IDs, gender, age and verified formats, for actor_id. Show preview_url as a markdown image; a personal actor's expires. actor_id is not combined with image, person or actor_gender. Free.

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": "list_actors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.39.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. First observedv0.20.0

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds two genuinely useful behavioral facts beyond that: preview_url should be rendered as a markdown image, and a personal actor's preview is time-limited. "Free" is a useful cost signal, but the rest of the behavioral picture (ordering, pagination, whether only saved/custom actors are returned versus stock ones) is absent.

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

Conciseness2/5

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

Three fragments separated by semicolons, one of which ("actor_id is not combined with image, person or actor_gender") is meaningless for a zero-parameter tool. The leading clause is reasonably front-loaded, but the middle and final clauses are confusing filler rather than earned content.

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

Completeness3/5

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

There is no output schema, so the description must carry return-value information, and it does partially: IDs, gender, age, verified formats, and preview_url usage. Coverage is incomplete for other likely fields (names, thumbnails, voice/format options) and "verified formats" is undefined, leaving the agent to discover the payload shape empirically.

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?

With zero parameters the baseline would be 4, but the description names actor_id, image, person, and actor_gender as if they were inputs and then says they are not combined. Since the schema has no properties at all, this text reads like it was copied from another tool and risks making the agent believe a filter exists that does not.

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

Purpose3/5

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

"Saved actors with IDs, gender, age and verified formats" identifies the resource but is a noun fragment with no verb, and it is really describing the returned fields rather than the operation. Nothing distinguishes it from siblings like create_actor, delete_actor, or get_actor_defaults, so the agent must infer 'list' from the name alone.

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?

There is no statement of when to call this versus create_actor, quote_actor, or get_actor_defaults. The only quasi-guidance is a rendering instruction for preview_url and the note that a personal actor's preview expires, which does not tell the agent when this tool is the right choice.

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