Create a new Leanpub bundle by providing a title, slug, and optional publisher ID to group books into a purchasable package.
Create a new Leanpub bundle.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| title | Yes | ||
| publisherId | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. The description merely restates the create action already implied by the tool name and does not explain side effects, idempotency, required permissions, validation behavior, or what the API returns on success 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no filler, redundant wording, or unnecessary detail. It front-loads the action and the target resource clearly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations, no output schema, and three undocumented parameters, a one-sentence description is far from complete. An agent lacks essential information about required inputs, expected values, and the result/return behavior needed to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the schema properties have no descriptions. The description does not explain the meaning of title, slug, or publisherId, or clarify which parameters are required and how they should be formatted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Create a new Leanpub bundle.' It clearly distinguishes this tool from the sibling create tools by naming a distinct product type (bundle vs. book, course, track).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use create_bundle versus create_book, create_course, or create_track. It also does not mention any prerequisite conditions, such as whether a publisher or existing book/course is required before creating a bundle.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.