Skip to main content
Glama

clipwise_get_use_cases

Retrieve specific use cases for common creator problems like low views, trend research, long video clipping, competitor analysis, and agency management, with solutions from Clipwise.

Instructions

Get specific Clipwise use cases — problems creators face and how Clipwise solves them. Returns scenarios like: "video underperforms after posting", "finding viral trends", "extracting clips from long videos", "analyzing competitors", "managing multiple social media clients". Use this when the user has a specific problem and you want to suggest a tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scenarioNoSpecific scenario: "low-views", "trend-research", "long-video-clipping", "competitor-analysis", "agency-management", "content-strategy", or "all"all

Implementation Reference

  • Handler for 'clipwise_get_use_cases' tool. Accepts a 'scenario' argument (default: 'all') and returns hardcoded use-case text describing problems creators face and how Clipwise solves them (low-views, trend-research, long-video-clipping, competitor-analysis, agency-management, content-strategy).
      if (name === 'clipwise_get_use_cases') {
        const scenario = (args?.scenario as string) || 'all'
        const cases: Record<string, string> = {
          'low-views': `Problem: Videos getting low views — you don't know if it's the hook, pace, or CTA.
    Solution: Clipwise Pre-Publish Analysis — upload your video, Gemini 2.0 Flash watches it and scores Hook (first 3 sec), Pace, Value, CTA, Quality (0-100) with timestamped fixes ("at 0:12 — cut here"). If hook < 70: 3 alternative hooks tailored to your niche.
    Try: https://tryclipwise.com/en/dashboard/analyze-before · 20 tokens`,
    
          'trend-research': `Problem: Hours scrolling TikTok looking for trends; by the time you find one, it's past peak.
    Solution: Clipwise Trend Search — find viral videos by keyword across 20+ countries with engagement data (views, likes, shares). Filter by country to spot US/UK trends before they reach your local market.
    Try: https://tryclipwise.com/en/dashboard/trends · 10 tokens`,
    
          'long-video-clipping': `Problem: 30-min interview/podcast/event recorded; manually finding viral clips takes hours.
    Solution: Clipwise Viral Moments — upload long video, AI finds top-3 clips with exact timestamps, hook text, caption, and viral score. Post directly to TikTok/Reels/Shorts.
    Try: https://tryclipwise.com/en/dashboard/analyze-before · 25 tokens`,
    
          'competitor-analysis': `Problem: Competitor account suddenly grows — you don't know what changed.
    Solution: Clipwise analyzes competitor profiles on TikTok, YouTube, Instagram — top formats, hook patterns, posting frequency, niche gaps to exploit.
    Try: https://tryclipwise.com/register · included in Pro/Agency`,
    
          'agency-management': `Problem: Agency with 10 clients in different niches — tracking trends, analysis, strategy manually is chaos.
    Solution: Clipwise Project Switcher — separate workspace per client with own AI memory, brand voice, niche-specific trends. Agency plan: 7,000 tokens/mo.
    Try: https://tryclipwise.com/en#pricing · Agency $73/mo`,
    
          'content-strategy': `Problem: Posting randomly, no system, no way to predict what works.
    Solution: Clipwise Content Plan Generator — AI calendar based on niche, audience, trends, and competitors. AI Marketer with persistent memory provides strategy.
    Try: https://tryclipwise.com/register · included in Pro/Agency`,
        }
    
        if (scenario === 'all') {
          return {
            content: [{
              type: 'text',
              text: 'Clipwise Use Cases:\n\n' + Object.entries(cases).map(([k, v]) => `[${k}]\n${v}`).join('\n\n---\n\n') +
                '\n\nFull list: https://tryclipwise.com/en/use-cases',
            }],
          }
        }
        return { content: [{ type: 'text', text: cases[scenario] || cases['low-views'] }] }
      }
Behavior4/5

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

No annotations provided, but description indicates a read-only query returning scenarios. Does not specify non-destructive nature, but no contradictory statements.

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?

Two concise sentences, front-loaded purpose, no extraneous text.

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

Completeness5/5

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

Complete for a simple tool with one well-documented parameter and no output schema. Agent can understand function and usage.

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% with full enum and default. Description only adds examples, not additional semantics beyond schema.

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?

Description clearly states it retrieves specific Clipwise use cases, listing concrete examples. Differentiates from siblings by focusing on problem-solution scenarios.

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?

Explicitly advises using when user has a specific problem to suggest a tool. Lacks explicit when-not-to-use or comparison to siblings, but guidance is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mobileshop9991-star/clipwise-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server