Skip to main content
Glama

Kubeez

get_skill

Read-onlyIdempotent

Scope: none (any authenticated key). Fetch the full markdown body of a kubeez skill by name. USE THIS as the universal fallback when your MCP client cannot read MCP resources (e.g. the Claude.ai web app does NOT expose resources/read to the model) or cannot fetch arbitrary HTTPS URLs (e.g. Claude.ai web's web_fetch only allows URLs that came from the user message or a prior tool/search result, so model-constructed URLs like https://mcp.kubeez.com/skills/viral-carousel.md get blocked). Tool calls always work in every MCP client, so this path is bulletproof.

AVAILABLE SKILLS: • content-creation — quality bar + propose-before-generate for posts/blogs/ads • social-post — single-image social/ad post = a DESIGNED creative (hook headline rendered on the image + caption), NOT a bare photo; 6 archetypes + prompt bar • marketing-campaign — niche-aware visual genre cheat sheet for marketing assets • viral-carousel — design modes (named style, reference, or a bespoke Art director system) + archetypes + prompt-construction bar for multi-slide IG/LinkedIn carousels (fetching via THIS tool also appends the user's recent deck history for anti-repeat — prefer it over resources/read for carousels) • carousel-style-previews — carousel style library: the 9 named styles (The Press, The Modernist, The Dossier, The Billboard, The Index, The Photograph, The Moleskine, The Whiteboard, The Screenshot) with preview URLs, plus palettes, card treatments, type pairings, mark styles and deck recipes • model-selection — picking the right image/video/audio model from get_models • media-upload — required when user has a local file (3-step upload flow) • asset-library — persistent named media (logos, references, songs) • billing-confirmation — preview cost before per-duration jobs (Kubeez has NO refunds) • polling — first-poll delays per media type, then every 5s • video-extend — extending Veo 3.1 clips via generation_type='extend' • seedance-2-tiers — Seedance 2.5 vs Seedance 2 / Fast / Mini disambiguation • seedance-2-5-prompting — writing the seedance-2-5 prompt itself: material roles, @Image N mapping, keyframes, storyboards, blockouts, long-video staging, 10000-char cap • critique — the 6-point rubric you (the calling LLM) run on your own output before shipping • marketing-strategy — hooks, platform-native copy formats, funnel/CTA matching, paid-ad angle system + character limits (the COPY twin of content-creation) • product-marketing — foundation context doc (product / audience / positioning / customer language) that copywriting, email-marketing, and launch read first • copywriting — off-image conversion copy: landing/pricing/feature pages, headlines, CTAs, value framing, 7-sweep editing pass • email-marketing — lifecycle sequences (welcome / nurture / onboarding / win-back) + B2B cold outreach and follow-ups • launch — launch playbook: announcement sizing, owned/rented/borrowed channels, five phases, checklist • anti-slop : the shared quality floor read alongside any task skill: visual and spoken slop tells, photoreal person module, negative-direction blocks, claims floor • ugc-video : creator-style / UGC / TikTok-style video: anti-polish contract, five arcs, hook gate, truth contract, frozen-frame QA • faceless-video : narrator-led video with nobody on camera: the one-call ceiling, script spine, style lock, captions pass • product-photoshoot : packshots, marketplace whites, lifestyle, in-hand, flatlay, hero banners, ad packs, try-on, conceptual product stills; product identity lock + recipes • thumbnail-generation : YouTube thumbnails and reel / podcast / video covers: concept frameworks, emotion casting, safe zones, 2 to 4 word text rules • character-sheet : turnaround / expression / model sheets as an identity anchor, plus how to reuse it (asset library, Seedance refs, Gemini Omni characters, Kling elements) • brand-mockups : the real logo on merch, packaging, signage, stationery, screens, brand boards; logo-maker when there is no logo yet • gemini-tts-expressive : expressive, tagged, accented or non-English TTS via generate_dialogue(provider='google') • seed-audio-prompting : prompt-driven speech via generate_dialogue(provider='seed'): prompt structure, voice references, audio_config

Returns: { name, uri, url, content_type, content } where content is the full skill markdown body. Same source-of-truth as the kubeez://skills/ MCP resource and the https://mcp.kubeez.com/skills/.md HTTPS endpoint — pick whichever path your runtime supports. CALL THIS BEFORE generate_media / generate_music / generate_dialogue when the matching skill applies; firing those tools without the relevant skill loaded leads to AI-slop output and wasted credits.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description adds the genuinely useful fact that resource, HTTPS, and tool paths are the same source-of-truth, plus a per-skill side effect (viral-carousel appends recent deck history). That side effect is mentioned but not explained, and it sits uneasily next to readOnlyHint without being resolved. The restated return shape is largely redundant with the output schema.

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?

Front-loaded with scope, then purpose, then the fallback rationale, then the catalog — the ordering is right and the catalog earns its length because it is the parameter documentation. Some fat remains: "this path is bulletproof," the parenthetical re-explanations of Claude.ai quirks, and a return-value sentence duplicated from the output schema.

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?

For a one-parameter fetch tool with a large controlled vocabulary, everything an agent needs is present: what it returns, how it relates to the other two access paths, when to prefer it, and what each enumerated skill is for. An agent can select both the tool and the right name without opening any other artifact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is a 28-value enum, which the schema alone cannot disambiguate. The description annotates nearly every enum value with what that skill contains and when it matters (e.g. seedance-2-tiers as disambiguation, anti-slop as a shared quality floor), adding far more meaning than the bare enum list.

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?

"Fetch the full markdown body of a kubeez skill by name" gives a specific verb, resource, and return shape. It also explicitly positions itself against two alternatives (MCP resources/read and the HTTPS endpoint), so an agent knows exactly what this is and is not.

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?

It states when to use it (client cannot read resources or fetch arbitrary URLs), names the concrete failure modes that trigger it, gives a per-case override (prefer this over resources/read for viral-carousel), and states sequencing ("CALL THIS BEFORE generate_media / generate_music / generate_dialogue") with the cost of skipping it.

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