Skip to main content
Glama
Sign In
Clipwright

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read a workflow method

get_workflow
Read-only

Read a workflow method by method_id to retrieve required inputs, script rules, evidence, limitations, and availability. Use its method and capability digests to plan UGC or faceless video ads.

Instructions

Read one workflow method by method_id: required inputs, script rules, evidence, limitations and current availability. Free and read-only. Use the returned method and capability digests in a plan.

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": {
      "method_id": "<method_id>"
    },
    "name": "get_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
method_idYes

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. Addedv0.29.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint/destructiveHint, yet the description adds non-redundant context: the call is free (cost behavior) and reports "current availability," warning that the underlying method state can vary. Aside from a redundant "read-only" restatement, it discloses meaningful behavior beyond the structured fields.

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?

Two compact sentences with the scope front-loaded and no filler. Minor friction: "capability digests" appears in the usage sentence but not in the enumerated return list, so the reader has to infer it is part of the payload.

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?

For a one-parameter read tool with no output schema, the description usefully sketches the return payload, which is the right use of the space. The gap is upstream: an agent is told to supply method_id but not how to discover a valid one, which matters given the many sibling list_* tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single method_id parameter has 0% schema description coverage, so the description must carry the semantics and largely does not: it never says what a method_id is, where to obtain one (presumably from list_workflows), or that it is a bounded-length string. Naming the parameter is not the same as explaining it.

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?

States a specific verb and resource ("Read one workflow method by method_id") and enumerates the returned facets: required inputs, script rules, evidence, limitations, availability. It is clearly distinguishable from list_workflows and get_workflow_plan by the singular 'one ... by method_id' scope, though no sibling is named explicitly.

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 closing sentence gives forward guidance ("Use the returned method and capability digests in a plan"), which orients usage, but there is no explicit when-not guidance and no named alternative such as list_workflows for discovery or get_workflow_plan for plan retrieval. Usage is implied rather than routed.

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