Skip to main content
Glama

generate_ebook

Start generating a complete multi-chapter eBook using AI. The price depends on the book (length, genre, theme and chapters) and is charged per token at the same rate as the Basic token pack on scrivibe.com, plus any applicable tax. Returns the exact price and a payment link that the user must visit to pay before generation begins. After payment, use get_job_status to track progress.

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": {
      "title": "<title>",
      "chapter_count": "<chapter_count>",
      "author": "<author>",
      "genre": "<genre>",
      "subject_theme": "<subject_theme>",
      "target_audience": "<target_audience>",
      "tone": "<tone>",
      "language": "<language>",
      "length": "<length>"
    },
    "name": "generate_ebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneYesWriting tone (e.g. 'professional', 'casual', 'academic', 'humorous').
emailNoBuyer's email address. If provided, enables invoice history and receipt delivery. Returning buyers with the same email share a single billing profile.
genreYesGenre name from list_genres (e.g. 'literature_fiction', 'nonfiction', 'romance').
titleYesThe title of the book
authorYesAuthor name for the book.
lengthYesBook length: short (50-100 pages), medium (100-200), long (200-300), epic (300+).
languageYesISO 639-1 language code: ar, de, en, es, fr, hi, id, it, ja, ko, pl, pt, ru, tr, zh.
descriptionNoBook description/premise/blurb to guide the AI generation.
chapter_countYesNumber of chapters to generate (1-50).
subject_themeYesSubject theme within the genre, from list_genres (e.g. 'nonfiction_biographies_memoirs').
chapter_lengthNoHow the book's length is spread across chapters.
narrative_voiceNoNarrative voice (e.g. 'first_person', 'third_person').
target_audienceYesTarget audience (e.g. 'beginners', 'young adults', 'professionals').
unique_elementsNoElements that make this book different.
references_sourcesNoResearch seed: facts, sources and URLs the book should be based on.
content_restrictionsNoContent to avoid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / chapter_length
      Added value: +{
      +  "description": "How the book's length is spread across chapters.",
      +  "enum": [
      +    "short_uniform",
      +    "medium_uniform",
      +    "long_uniform",
      +    "naturally_varied",
      +    "progressive"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / content_restrictions
      Added value: +{
      +  "description": "Content to avoid.",
      +  "type": "string"
      +}
    • changedInput schema / properties / genre / description
      Previous value: -"Genre name from list_genres (e.g. 'literature_fiction', 'nonfiction', 'romance'). Defaults to 'literature_fiction'."New value: +"Genre name from list_genres (e.g. 'literature_fiction', 'nonfiction', 'romance')."
    • changedInput schema / properties / language / description
      Previous value: -"ISO 639-1 language code (e.g. 'en', 'es', 'fr'). Defaults to 'en'."New value: +"ISO 639-1 language code: ar, de, en, es, fr, hi, id, it, ja, ko, pl, pt, ru, tr, zh."
    • addedInput schema / properties / length
      Added value: +{
      +  "description": "Book length: short (50-100 pages), medium (100-200), long (200-300), epic (300+).",
      +  "enum": [
      +    "short",
      +    "medium",
      +    "long",
      +    "epic"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / narrative_voice
      Added value: +{
      +  "description": "Narrative voice (e.g. 'first_person', 'third_person').",
      +  "type": "string"
      +}
    • addedInput schema / properties / references_sources
      Added value: +{
      +  "description": "Research seed: facts, sources and URLs the book should be based on.",
      +  "type": "string"
      +}
    • addedInput schema / properties / subject_theme
      Added value: +{
      +  "description": "Subject theme within the genre, from list_genres (e.g. 'nonfiction_biographies_memoirs').",
      +  "type": "string"
      +}
    • addedInput schema / properties / unique_elements
      Added value: +{
      +  "description": "Elements that make this book different.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "title",
      -  "chapter_count"
      -]New value: +[
      +  "title",
      +  "chapter_count",
      +  "author",
      +  "genre",
      +  "subject_theme",
      +  "target_audience",
      +  "tone",
      +  "language",
      +  "length"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does real work: it discloses the billing model (per token at the Basic pack rate plus tax), the cost drivers (length, genre, theme, chapter count), and the critical precondition that generation does not begin until the payment link is visited. It omits idempotency, rate limits, and what happens on abandonment or failure.

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?

Four tight sentences, each adding a distinct fact: what is generated, what it costs, what is returned and must happen next, and which tool follows. The return/payment precondition is front-loaded before the handoff instruction.

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?

For a 16-parameter, no-annotation, no-output-schema mutation-like tool, the description covers the essential unknowns: cost source, the pay-before-generate gate, return payload, and next step. Remaining gaps (failure/refund behavior, whether an unpaid job expires) are secondary but not trivial.

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 the baseline is 3; the description adds value by naming which parameters actually drive cost ('length, genre, theme and chapters'), giving the agent a reason to reason carefully about those inputs. It adds nothing about the remaining dozen parameters, but the schema already documents them fully.

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 ('Start generating a complete multi-chapter eBook using AI') and immediately clarifies what the call returns (price + payment link), which is not obvious from the name. The final sentence routes to get_job_status, so an agent can distinguish this initiation step from the tracking and retry siblings.

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?

Provides an explicit ordered workflow: call this, the user pays via the returned link, then poll get_job_status. It does not address when not to use it (e.g. an existing unpaid job, or retry_job for a failed one), so the exclusions half of the guidance is absent.

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