Moltline Creator Studio

This connector has been deprecated

Superseded listing, not a dead server. This entry was imported from an early Glama registration under com.moltlinestudio.mcp; the same server is listed under its official MCP Registry name — use com.moltlinestudio/creator. Endpoint unchanged: https://mcp.moltlinestudio.com/creator — still live, still free on the free tier. Only this duplicate entry is deprecated.

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-keeper"} 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.

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

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / slug / description

Previous value: -"Product slug exactly as returned by list_products,\ne.g. \"brand-voice\"."New value: +"Product slug exactly as returned by list_products,\ne.g. \"brand-voice-keeper\"."

First observedAug 17, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Goes beyond the annotations by publishing an error contract: invalid, missing, or malformed input never raises a protocol error but returns {"error": "<what is wrong and how to fix it>"} with a concrete example. It also flags the PREMIUM/license nature of the resource, which no annotation conveys. It does restate read-only and idempotent, which the annotations already declare, so it falls short of the top score.

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?

Front-loads the one-line purpose and the premium note, then examples, then routing, then error semantics – a sensible order for skimming. Some redundancy exists ("persona plus every skill" is stated twice), but it is short and every block carries distinct information.

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?

Covers purpose, routing, error behavior, and retry safety, and an output schema exists so return values need not be spelled out further. For a single-parameter read tool, an agent has everything needed to call it correctly and handle failures.

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% and the slug description already points at list_products, so the schema does the heavy lifting. The description still adds value with a concrete input/output example pair ({"slug": "brand-voice-keeper"} → persona plus skills array), which shows the caller what the slug should look like in practice.

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?

States a specific verb and resource ("Load one product in full: its persona plus every paid skill") and immediately scopes what "full" means. It also names the siblings it is not: get_full_skill, get_free_skill, and list_products.

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 gives the selection condition ("Use when the caller wants the whole product") and two exclusions with the alternatives that cover them ("Not for a single skill (get_full_skill) and not for a free look, which list_products and get_free_skill provide"). Nothing about routing 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.

All Moltline Creator Studio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?