Skip to main content
Glama

FreeDailyPro Book Publishing Tools

publishing_kdp_description

Read-onlyIdempotent

Book description HTML formatter

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "publishing_kdp_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNoHTML to clean to the tags KDP allows; what was removed or changed is reported. Script, style, head, title and noscript elements are removed with their content; if one is never closed, everything after its opening tag is removed too.
textNoPlain text; blank lines make paragraphs. null is treated as omitted. Send text or html. Missing, empty and whitespace-only input all return the same 400 "Send text or html.". html wins when both have content.
headingNoTag used for headings. Default h4. null is treated as omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / heading / description
      Previous value: -"Tag used for headings. Default h4."New value: +"Tag used for headings. Default h4. null is treated as omitted."
    • changedInput schema / properties / text / description
      Previous value: -"Plain text; blank lines make paragraphs. Send text or html. Missing, empty and whitespace-only input all return the same 400 \"Send text or html.\". html wins when both have content."New value: +"Plain text; blank lines make paragraphs. null is treated as omitted. Send text or html. Missing, empty and whitespace-only input all return the same 400 \"Send text or html.\". html wins when both have content."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Changed2 schema fields changed
    • changedInput schema / properties / html / description
      Previous value: -"HTML to clean to the tags KDP allows; what was removed or changed is reported."New value: +"HTML to clean to the tags KDP allows; what was removed or changed is reported. Script, style, head, title and noscript elements are removed with their content; if one is never closed, everything after its opening tag is removed too."
    • changedInput schema / properties / text / description
      Previous value: -"Plain text; blank lines make paragraphs. Send text or html (html wins when both are sent)."New value: +"Plain text; blank lines make paragraphs. Send text or html. Missing, empty and whitespace-only input all return the same 400 \"Send text or html.\". html wins when both have content."
  4. Changed3 schema fields changed
    • addedInput schema / properties / heading / description
      Added value: +"Tag used for headings. Default h4."
    • changedInput schema / properties / html / description
      Previous value: -"HTML to clean to the tags KDP allows"New value: +"HTML to clean to the tags KDP allows; what was removed or changed is reported."
    • changedInput schema / properties / text / description
      Previous value: -"Plain text; blank lines make paragraphs"New value: +"Plain text; blank lines make paragraphs. Send text or html (html wins when both are sent)."
  5. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not mention the 400 error on missing input, the removal-report behavior, or that html takes precedence when both fields are present (those details live only in the schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four words with no padding, but the brevity comes from under-specification rather than discipline. It is front-loaded but carries almost no information an agent could act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple, side-effect-free transform with three fully documented parameters, so the schema carries most of the burden. However, with no output schema, the description should at least say the tool returns cleaned HTML plus a record of removed/changed markup — a key consumer-facing behavior it omits.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema itself explains html vs text precedence, null handling, and the heading enum default. The description adds no parameter meaning of its own, so the baseline 3 for fully documented schemas applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Book description HTML formatter" identifies the resource (KDP book description) and gestures at a transformation (format/clean HTML), but the verb is nominal and vague. It does not say the tool sanitizes HTML to KDP-allowed tags, converts plain text into paragraphs, or returns a report of what was removed — all facts an agent would want from the purpose statement.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no indication that this should be called before submitting a description to KDP, no mention of alternatives, and no exclusions. The sibling list (ISBN, ONIX, royalty, spine width) is unrelated, so routing risk is low, but the description itself provides no guidance.

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