Skip to main content
Glama

Moltline Creator Studio

by com.moltlinestudio

Get Full Product

get_full_product
Read-onlyIdempotent

Load one product in full: its persona plus every paid skill. PREMIUM (license).

Typical input {"slug": "brand-voice"} returns {"slug": ..., "name": ..., "persona": "", "skills": [{"name": ..., "instructions": ...}, ...], "free_skill": {...}}.

Returns persona plus every skill for one product. Use when the caller wants the whole product. Not for a single skill (get_full_skill) and not for a free look, which list_products and get_free_skill provide with no plan. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "unknown slug ''"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesProduct slug exactly as returned by list_products, e.g. "brand-voice".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds critical behavior: error handling never raises protocol errors but returns structured error objects with fix guidance. It confirms read-only and idempotent nature with explicit retry safety. Also discloses license restriction (PREMIUM) not present in annotations.

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?

The description is about 150 words, front-loaded with the core purpose, followed by example, usage guidance, and error handling. It is well-structured and each sentence earns its place. A slight trim could be possible, but it remains efficient and scannable.

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?

Given the tool has one parameter and an output schema, the description fully covers input, output (high-level structure shown), error behavior, licensing, and safe retry. It leaves no major gaps for an agent to understand invocation, safety, and alternatives.

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

Parameters4/5

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

Schema coverage is 100% for the single parameter 'slug', with a detailed description. The description adds value by giving a typical input example and showing the expected output structure, which helps the agent understand parameter usage in context. However, the schema already carries the parameter description well, so the incremental semantic addition is moderate.

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?

The description clearly states the tool loads one product in full, including persona and every paid skill. It differentiates from siblings by explicitly noting when to use (whole product) and when not to (single skill via get_full_skill, free look via list_products/get_free_skill). The verb 'load' plus specified resource makes purpose unambiguous.

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?

Explicitly states 'Use when the caller wants the whole product' and lists alternatives: Not for a single skill (get_full_skill), not for a free look (list_products/get_free_skill). It also mentions the PREMIUM license requirement, giving clear context and exclusion criteria.

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

All Moltline Creator Studio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct function: writing analysis, headline ranking, reading time, social length check, product listing, free skill retrieval, full product retrieval, and paid skill retrieval. There is no overlap, and the descriptions clearly differentiate them.

Naming Consistency3/5

Tool names use mixed conventions: imperative verbs (get_, list_) for product tools, but descriptive nouns for writing tools (headline_analyzer, reading_time, social_length_check). While not chaotic, the lack of a uniform pattern could cause minor confusion.

Tool Count5/5

With 8 tools covering two related areas (writing analysis and product catalog), the count is well-scoped. Each tool serves a clear purpose without redundancy, fitting the server's 'creator' theme.

Completeness4/5

The writing tools cover major content needs (draft quality, headlines, reading time, platform limits). The product tools provide complete read-only access to the catalog. A minor gap is the lack of search or filtering, but list_products returns all 20 products, which is adequate.

Resources