Skip to main content
Glama

Caelara Labs Social Analytics

reels_hook_scorer

Score the opening hook of a Reel/Short/TikTok script or caption

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": {
      "text": "<text>"
    },
    "name": "reels_hook_scorer"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesScript or caption (first lines matter most)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and discloses very little. It does not say whether scoring is a numeric scale, a rubric with sub-dimensions, or a qualitative critique, nor whether it is a pure read/analysis operation or produces side effects.

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?

A single front-loaded sentence with no filler words, and the verb/resource lands immediately. It is efficient, but its brevity borders on under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter analysis tool with no output schema, the description should at minimum describe what a "score" returns (scale, criteria, or critique form). That key detail is absent, leaving the agent unable to predict the response shape.

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% and the single parameter is already documented as "Script or caption (first lines matter most)". The description restates the same idea without adding format, length, or input-quality constraints, so the schema does the real work.

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 ("Score") and a specific resource ("opening hook") plus the content types it applies to (Reel/Short/TikTok script or caption). An agent can tell this apart from caption_hashtag_extractor or video_viral_audit_composite, though it does not explicitly name a sibling to route against.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative guidance is given. The agent must infer that this is a single-piece critique tool rather than the broader video_viral_audit_composite, with nothing in the text confirming or denying that 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