Skip to main content
Glama

hooks_generate

Write hooks (the first line or first 2 seconds of a post) for this brand, each scored 0-100 with its pattern, an estimated percentile and why it works. Best first. Free (no credits). Written from the brand profile when there is one; without one (brand_profile finds nothing) give a topic and they are written for it. Aim it with a topic, an audience id from brand_profile and the platform. Pick the best hook and pass it as "hook" to studio_generate, or use it as the first line of a post.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many hooks (default 10)
topicNoWhat the hooks are about, e.g. "our new invoice scanner"
platformNoWhere it will be posted (default tiktok)
audienceIdNoAn audience id from brand_profile (default: the main audience)

Output Schema

NameRequiredDescriptionDefault
errorNo
hooksNo
audienceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds behavior the annotations don't carry: the call is free with no credits consumed, and generation degrades gracefully to topic-based output when no brand profile exists. The annotations already declare a non-read-only, non-destructive, non-open-world operation, so that ground is covered; what's missing is anything about generation time or failure modes.

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?

Three tight sentences: what it produces, what it needs, and where the output goes. The most decision-relevant facts (scoring, free, brand-profile fallback) are front-loaded with no filler.

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?

Return shape is covered by the output schema and cost, prerequisites, and downstream wiring are all stated, which is more than most tools of this complexity disclose. Minor gaps remain around latency and how audienceId affects results, but nothing blocks a correct call.

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 100%, so the baseline is 3; the description goes beyond it by explaining the conditional relationship between brand profile and topic, and that audienceId must come from brand_profile. It doesn't clarify how count interacts with scoring or how platform alters hook style.

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 ('Write hooks') and parenthetically defines the artifact ('the first line or first 2 seconds of a post'), plus what comes back (scored 0-100, pattern, percentile, why it works). It never names the sibling hooks_score, so an agent must infer the generate-vs-score split rather than being told it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly covers the two operating modes: written from the brand profile when one exists, and from a supplied topic when brand_profile finds nothing. It also explains how to aim the call (topic, audience id from brand_profile, platform) and routes the result into studio_generate or a post, which leaves little to inference.

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