Skip to main content
Glama

Verity Analytics

predict_hook_retention

Analyze opening 30-second video hooks to predict audience retention curves (0-100 score) and script optimization recommendations. Counts toward the 5-scan annual free allowance.

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": {
      "hook": "<hook>"
    },
    "name": "predict_hook_retention"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookYesOpening video script lines or hook transcript to audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden, and it leaves real gaps: nothing says whether the operation is read-only or mutates stored data, what happens on failure, or how long analysis takes. It does disclose a consumption trait ('Counts toward the 5-scan annual free allowance'), which is valuable and unusual, plus the output shape, so it is not empty.

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?

Two sentences, both earning their place: the capability and its outputs come first, then the quota constraint. Nothing is redundant or buried, and the structure is front-loaded.

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 analysis tool with no output schema, the description covers purpose, reported outputs, and a quota cost. The main missing piece is the behavioral profile (safety/reversibility), which matters more here because no annotations exist.

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 single 'hook' parameter is fully documented in the schema itself. The description adds only the 'opening 30-second' scoping, which slightly narrows what text to submit but gives no format, length, or content guidance beyond the schema's minLength/maxLength.

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 names a specific verb ('analyze'), a specific resource ('opening 30-second video hooks'), and the outputs ('retention curves (0-100 score) and script optimization recommendations'). This is enough to separate it from scan_niche_demand and synthesize_omnichannel_assets, though it never explicitly contrasts itself with them.

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 only implied: the agent infers it should submit a hook transcript for auditing. There is no statement of when to prefer this over the sibling scan or synthesis tools, no prerequisites, and no exclusions. The quota sentence is a cost signal rather than when-to-use guidance.

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