Performs a batch get to retrieve multiple items from Audiobookshelf in one POST request.
Create or act on batch get.
POST /api/items/batch/get
Args: body: Request payload. Read the matching GET or the /schema endpoint first to see the fields this resource expects.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide idempotentHint=true and destructiveHint=false, but the description adds nothing about behavior. It doesn't clarify whether the operation is read-only or mutating, and the phrase 'Create or act' is ambiguous. No side effects or response details are disclosed.
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 brief but under-specified. It contains two sentences, but they are unhelpful, so it's not effective conciseness; it's just lacking content.
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?
The description is extremely incomplete. It doesn't explain what the body should contain, what the response looks like, or how to use the tool effectively. The existence of an output schema is not leveraged, and the description provides no context about the batch get operation.
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?
The only parameter is 'body' with additionalProperties:true and no schema description. The description only says 'Read the matching GET or the /schema endpoint first', which is a pointer, not actual semantics. Since schema coverage is 0%, the description fails to compensate.
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 says 'Create or act on batch get' which is vague and doesn't clearly state what the tool does. It provides the endpoint but not the operation's purpose, and doesn't distinguish it from siblings like create_items_batch_delete or create_items_batch_update.
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 this tool versus alternatives. There are many batch operations, and the description doesn't mention conditions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.