Skip to main content
Glama
UserClimb

UserClimb

by thomaslrw

Get short video structures

get_video_structures
Read-only

Retrieve proven short-video structures with hook patterns, beat-by-beat shapes, and the metrics each earns. Pass an app type to rank structures and engagement rules for your niche.

Instructions

Proven structures for short videos (Reels, TikToks, Shorts), each with its hook pattern, the shape beat by beat, what it earns (watch time, sends, saves or comments) and the ask that fits. Pass an app type to rank them for that kind of app. Includes the engagement rules.

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

Input Schema

NameRequiredDescriptionDefault
app_typeNoOptional. Ranks the structures for this kind of app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by describing the return payload's composition and the ranking behavior keyed on app_type, plus a mention of included engagement rules. It stops short of stating how many structures are returned or how the output is formatted.

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?

Three tight sentences with the resource and its contents front-loaded, then the parameter behavior, then an inclusion note. The phrase 'the shape beat by beat' is slightly informal but informative; nothing is 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?

There is no output schema, so the description carries the burden of describing the response, and it does so concretely by listing the four components of each structure. Given one optional parameter and read-only annotations, the definition is nearly complete, missing only output shape/volume details.

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% and the single enum parameter is fully documented, so the schema does the heavy lifting. The sentence 'Pass an app type to rank them for that kind of app' restates the schema's own wording about ranking rather than adding format, default-ordering, or behavior-when-omitted detail. A 3 baseline is appropriate.

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 resource (short video structures for Reels, TikToks, Shorts) and enumerates its contents — hook pattern, beat-by-beat shape, payoff, and the ask — so an agent knows exactly what comes back. It does not differentiate itself from siblings like get_hooks or get_playbook, which overlap conceptually, leaving the agent to guess at the boundary.

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?

The description explains how to use the optional parameter ('Pass an app type to rank them'), which is useful call-time guidance. However, it never says when to choose this tool over get_hooks or get_playbook, nor does it state any precondition or exclusion, so routing between overlapping siblings remains an inference.

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