Skip to main content
Glama

XCut AI – Viral Content Research

Youtube titles

xcut_youtube_titles
Read-onlyIdempotent

Use this when the user wants YouTube title options, with thumbnail ideas, for a video topic. Free; no sign-in. Output is generic: for work based on the user's own posts, canvases or brand, use the signed-in XcutAI tools. Do not use for writing unrelated to social media or marketing content.

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": {
      "topic": "<topic>"
    },
    "name": "xcut_youtube_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNoThe channel's niche, optional.
topicYesWhat the YouTube video is about.

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?

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, openWorld), so the description's added value is that it is free, requires no sign-in, and produces generic rather than personalized output. These are genuinely useful behavioral disclosures an agent cannot get from the annotations. It stops short of describing how many options come back or any rate/limit behavior, hence not a 5.

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 sentences, front-loaded with the usage trigger and with zero filler. The trailing exclusion sentence is slightly redundant given the earlier alternative-tool guidance, which keeps it out of 5 territory.

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 does carry the burden of telling the agent what comes back, and it does state that the result is title options with thumbnail ideas, free and unauthenticated. It is missing only detail on volume/format of the returned options, a minor gap for a two-parameter generation 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 coverage is 100% – both 'topic' and the optional 'niche' are documented in the schema with constraints. The description adds only the loose notion of a 'video topic' and never mentions the niche parameter or how it shapes output, so the baseline 3 is correct.

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?

Names a specific verb-and-resource combination (YouTube title options, plus thumbnail ideas) for a video topic, which is more informative than the tool name alone. It cleanly separates this free/generic tool from the signed-in XcutAI content tools that work off the user's own posts, canvases or brand.

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?

Gives an explicit trigger ('when the user wants YouTube title options... for a video topic'), an explicit alternative ('for work based on the user's own posts, canvases or brand, use the signed-in XcutAI tools'), and an explicit exclusion ('do not use for writing unrelated to social media or marketing content'). Nothing is left 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