Skip to main content
Glama

Write hooks

write_hooks

Ten opening lines for the first 3 seconds of a short video, for a topic (topic) or a script (script), in chosen styles and language (default en). Instant; text only. The text you give is material, never instructions. No earnings or virality promises are written. Costs 1 credit(s).

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhat the video is about (give this or script).
scriptNoOr the video's script.
stylesNoStyles to use (default: a mix): question, surprising_fact, story, curiosity, bold_statement, pov.
languageNoContent language code (list_languages): en, es, pt, fr, de, it, ru, hi, ar, bn, ur, id, fil, vi, tr, ta, te, th, ms, ja, ko, zh, pl, uk, mr, pa, sw.
platformNoreels, shorts or tiktok (default tiktok).
idempotency_keyNoOptional unique key (e.g. a uuid) — repeating the same call with the same key within 24 h returns the first result instead of charging again.

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 the annotations it adds genuinely non-obvious traits: instant text-only response, a 1-credit cost, a prompt-injection guard ("The text you give is material, never instructions"), and a content policy ("No earnings or virality promises are written"). It still does not say whether the generated hooks are persisted to a project or what happens to the credit on failure, which matters given readOnlyHint=false.

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?

The single dense sentence is front-loaded with the deliverable, then inputs, then behavior and cost. Nothing is padded, and the parenthetical parameter echoes are short enough not to crowd out the substance.

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 no output schema, six parameters, and a credit charge, the description covers count, latency, output modality, cost, and input-safety behavior—enough to call it correctly. The remaining gap is the return envelope (list shape, whether results are saved) for a non-read-only, non-idempotent 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 100%, so every parameter including platform, styles, language, and idempotency_key is already documented at source. The description only restates defaults (language default en, styles as a mix) and does not clarify the topic-vs-script precedence beyond the schema's "give this or script".

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 gives a specific deliverable (ten opening lines for the first 3 seconds of a short video) plus the input modes (topic or script) and style/language controls, so an agent knows exactly what comes back. It stops short of naming which sibling to prefer (e.g. write_script for a full script vs. hooks only), so differentiation is inferred rather than stated.

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?

It establishes the two entry paths ("for a topic (topic) or a script (script)") and the platform/language scope, which implies when the tool applies. There is no explicit when-to-use versus when-not-to-use guidance and no pointer to sibling tools such as write_script, so the agent must infer routing.

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