Skip to main content
Glama

Suggest Clip Hooks

hooks_suggest
Read-only

Suggest text hooks, existing transcript sentences and visual ranges without editing the project. Defaults to three per layer, count 1-5. Times use project timeline seconds. Included with a daily workspace cap; never starts media analysis. Unsupported options are omitted.

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": {
      "layers": "<layers>",
      "count": "<count>",
      "projectId": "<projectId>",
      "workspaceId": "<workspaceId>"
    },
    "name": "hooks_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYes
layersYes
projectIdYesUUID string.
workspaceIdYes

Output Schema

NameRequiredDescriptionDefault
textYes
spokenYes
visualYes
languageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint/destructiveHint=false, the description discloses genuinely new behavior: a daily workspace usage cap, that it never triggers media analysis, and that unsupported options are silently omitted, plus the units for returned times. These are exactly the side-effect and failure-mode facts annotations cannot carry. It stops short of explaining fallback behavior when the cap is exhausted.

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?

Four short sentences, front-loaded with the purpose and immediately followed by the highest-value constraints (defaults, units, cap, no analysis). No filler. 'Unsupported options are omitted' is the only slightly opaque line, but it carries real meaning about enum handling.

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?

With an output schema present, return values need not be described, and the description supplies the remaining essentials: per-layer defaulting, time units, the rate limit, and the no-analysis guarantee. A precondition such as requiring a prepared transcript for the 'spoken' layer would make it complete, but the core calling requirements are covered.

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

Parameters4/5

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

Schema description coverage is only 25% (only projectId has a description), so the description must compensate, and it does: it clarifies that count is per layer (not a total) with a 1-5 range, and its enumeration of text hooks / transcript sentences / visual ranges maps onto the text/spoken/visual layer enum. workspaceId and its null default remain unexplained, but the key ambiguity is resolved.

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 ('Suggest') and three concrete resources (text hooks, transcript sentences, visual ranges), and clarifies scope with 'without editing the project.' It does not name a sibling alternative, but 'never starts media analysis' implicitly distinguishes it from analysis-triggering tools, so an agent can place it without opening a schema.

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?

Usage is implied rather than stated: the read-only framing and the 'never starts media analysis' clause tell the agent this is a non-mutating suggestion step, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The daily workspace cap hints at a throttling constraint but not at how to route between tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources