Moltline Creator Studio

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

Name	Required	Description	Default
`slug`	Yes	Product slug exactly as returned by list_products, e.g. "brand-voice".

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds error behavior details (never raises protocol error, returns error object with fix guidance) and reaffirms idempotency/read-only nature, providing valuable context beyond annotations.

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?

Description is well-structured with a front-loaded purpose, example, usage guidance, error handling, and idempotency note. Every sentence adds value, no redundancy.

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 presence of an output schema, the description compensates with a JSON output example. It covers licensing, error behavior, retry safety, and distinction from sibling tools. Sufficient for a simple 1-parameter tool.

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 description coverage is 100% with a clear parameter description. The description adds an inline example of typical input, which reinforces parameter usage but doesn't add substantial new meaning beyond the schema. Baseline 3 with slight improvement for contextual example.

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 it loads a full product with persona and all paid skills, using specific verbs and resource. It distinguishes from siblings like get_full_skill and list_products, making 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 when to use 'when the caller wants the whole product' and when not—for single skill or free look—naming specific alternative tools (get_full_skill, list_products, get_free_skill). Also mentions license requirement.

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 tools Inspect

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.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: prose analysis, headline scoring, reading stats, platform length check, product listing, free/paid skill retrieval, and full product details. There is no ambiguity between any pair of tools, and descriptions explicitly note what not to use them for.

Naming Consistency5/5

All tool names use consistent snake_case verbs followed by nouns (e.g., analyze_writing, list_products, get_free_skill). Even reading_time and social_length_check follow the pattern, albeit with nouns first, but the style is uniform and predictable.

Tool Count5/5

With 8 tools, the server is well-scoped. It covers both content analysis (4 tools) and product catalog access (4 tools) without overloading or underrepresenting either domain. The number feels appropriate for a focused studio toolkit.

Completeness4/5

The tool set covers the core functions of a Creator Studio: writing analysis, headline optimization, reading time, social length checks, plus full product catalog introspection. Minor gaps like grammar checking or content generation exist but are outside the stated scope. The set has no dead ends for the intended workflows.

Resources

Need Help?