Skip to main content
Glama

Suggest UGC hooks

autoshort_ugc_suggest_hooks

Generates 10–20 UGC hook options from a campaign's app description, filters out unsupported income or result promises, and lets the user choose the hooks to use.

Instructions

Propose 10-20 hooks for a campaign from its app description, in the families "I can't believe…", "No one told me…", "POV: …", "X months of … and now I find this" and a pricing angle. An honesty filter drops income or results promises, testimonial stats and speed claims the app cannot back up. Free, but needs a positive credit balance; max 20 per hour. Show the hooks to the user and let them pick.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "autoshort_ugc_suggest_hooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
campaignIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (which only declare non-read-only, non-idempotent, open-world, non-destructive), the description discloses an honesty filter with concrete rejection categories, the cost model ('Free, but needs a positive credit balance') and a rate limit ('max 20 per hour'). It also flags that the output is meant for user selection, which materially shapes how the agent should handle the result.

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?

Four front-loaded sentences: purpose, the enumerated families, the honesty filter, the cost/rate constraints, and the workflow. The family list is long but is functional content, and no sentence is redundant.

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, the description should characterize the return value; it says hooks are proposed and meant for user selection but does not say whether they are persisted, returned with IDs, or regenerated on repeat calls (relevant given idempotentHint=false). Cost, rate limit and filtering behavior are otherwise well covered for a two-parameter tool.

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 0% for both parameters, so the description carries the burden. It effectively explains the count parameter by stating '10-20 hooks' and 'max 20', matching the schema's minimum/maximum, and hints that campaignId supplies the app description. However, it never explicitly ties these to the parameter names or explains what a campaignId must reference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Propose 10-20 hooks for a campaign') and additionally enumerates the hook families produced, so an agent knows exactly what output to expect. No sibling tool in the list performs hook suggestion, so the scope is unambiguous without naming an alternative.

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

Usage Guidelines4/5

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

It states the input dependency (the campaign's app description) and gives a follow-on workflow instruction ('Show the hooks to the user and let them pick'), which tells the agent this is a human-in-the-loop step. It stops short of naming when-not-to-use this tool or pointing to any alternative, so it is clear context rather than full routing guidance.

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