FableMaker

by io.github.itpofy2024o

create_story

Generate a new story from your idea. Creates an illustrated storybook (MD), an AI song, or an AI drama video. Returns a storyId immediately — processing happens in the background. Use get_story to check progress.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	script=illustrated storybook, song=AI music with cover art, drama=AI video
`title`	No	Story title (optional, defaults to "Untitled")
`outputs`	Yes	What to create: md (storybook), song, or drama (video)
`duration`	No	snappy=shorter/faster, exq=longer/higher quality, clappy=premium video (90-180s, new stories only). Default: snappy
`playStyle`	No	Writing style for play/screenplay: Oscar Wilde, Stan Lee, etc.
`songStyle`	No	Music artist style: Amy Winehouse, David Bowie, etc.
`storyIdea`	Yes	Your story idea, prompt, or description
`dramaStyle`	No	Director style for video: Quentin Tarantino, Christopher Nolan, etc.
`dramaTheme`	No	Video theme: standard (animation), scifi, mythical. Default: standard
`scriptStyle`	No	Writing style for storybook: William Shakespeare, Jane Austen, Charles Dickens, etc.
`songDuration`	No	snappy=~60sec, exq=1.5-3min (default: snappy)
`contextVersionIds`	No	Optional: link previous episodes for context. Use get_story to find version IDs.

TDQS

A4.4/5.0

Behavior4/5

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

Without annotations, the description discloses that processing is asynchronous and a storyId is returned immediately. It does not cover cost/credit consumption or rate limits, but the async behavior is a key behavioral trait well communicated.

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?

The description is two sentences with no unnecessary words. It front-loads the purpose and key behaviors, making it easy for an agent to quickly grasp the tool's function.

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?

Given 12 parameters and no output schema, the description covers core functionality and async behavior. It could benefit from mentioning customization options (styles, duration) but the schema handles those details. Overall adequate.

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%, so baseline is 3. The description adds value by mapping output types (e.g., 'script=illustrated storybook') and mentioning the use of get_story, which aids understanding beyond schema descriptions.

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's purpose: generating a story from an idea and creating specific media types (illustrated storybook, AI song, AI drama video). It distinguishes itself from sibling tools like get_story and delete_story by focusing on creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the async nature and directs users to get_story for progress checking. It does not explicitly mention when not to use the tool or compare to alternatives, but context implies this is the primary creation tool.

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

All FableMaker 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

A3.9/5.0

Disambiguation4/5

Tools have mostly distinct purposes. The only potential overlap is between create_story and quake_story, but quake_story is explicitly a 'do-over' with limitations, so confusion is minimal.

Naming Consistency4/5

Most tools follow verb_noun pattern (e.g., create_story, get_balance), but 'login' and 'signup' are single verbs, and 'quake_story' uses an unconventional verb. This is a minor inconsistency.

Tool Count5/5

With 10 tools covering account management, payments, story CRUD, and specialized operations (quake, remix), the count is well-scoped for the platform's purpose.

Completeness4/5

Covers core lifecycle (create, read, list, delete stories) plus payments and authentication. Missing update_story for editing metadata, but this is a minor gap.

Resources

Need Help?