mcp-medusa

Overview Schema Source Related Servers Discussions Admin

bulk_add_anime

Add multiple anime items at once. Use dry-run to preview which titles will be added, then set execute to true to write accepted entries while skipping rejected ones.

Instructions

Dry-run or add multiple anime items. Skips filterDecision=skip; execute must be true for writes.

Input Schema

TableJSON Schema

Name	Required	Default
`items`	Yes
`source`	No	myanimelist
`execute`	No
`root_dir`	No	/media/videos/Anime
`max_items`	No
`pause_seconds`	No
`decision_field`	No
`verify_attempts`	No
`allowed_decisions`	No
`verify_delay_seconds`	No
`initial_release_group`	No	SubsPlease
`fallback_release_groups`	No
`release_group_fallback_days`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv0.0.23Aug 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties / allowed_decisions / title
```
Removed value: -"Allowed Decisions"
```
- removedInput schema / properties / decision_field / title
```
Removed value: -"Decision Field"
```
- removedInput schema / properties / execute / title
```
Removed value: -"Execute"
```
- removedInput schema / properties / fallback_release_groups / title
```
Removed value: -"Fallback Release Groups"
```
- removedInput schema / properties / initial_release_group / title
```
Removed value: -"Initial Release Group"
```
- removedInput schema / properties / items / title
```
Removed value: -"Items"
```
- removedInput schema / properties / max_items / title
```
Removed value: -"Max Items"
```
- removedInput schema / properties / pause_seconds / title
```
Removed value: -"Pause Seconds"
```
- removedInput schema / properties / release_group_fallback_days / title
```
Removed value: -"Release Group Fallback Days"
```
- removedInput schema / properties / root_dir / title
```
Removed value: -"Root Dir"
```
- removedInput schema / properties / source / title
```
Removed value: -"Source"
```
- removedInput schema / properties / verify_attempts / title
```
Removed value: -"Verify Attempts"
```
- removedInput schema / properties / verify_delay_seconds / title
```
Removed value: -"Verify Delay Seconds"
```
- removedInput schema / title
```
Removed value: -"bulk_add_animeArguments"
```
- removedOutput schema / title
```
Removed value: -"bulk_add_animeDictOutput"
```
First observedv0.1.0Jun 25, 2026

TDQS

A3.7/5.0

Behavior3/5

Does 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. It does usefully state that items with 'filterDecision=skip' are skipped and that 'execute must be true for writes,' implying writes do not happen otherwise. However, it does not disclose behavior for non-skip decisions, partial failures, side effects on disk, or what response the agent should expect. This is minimally transparent but far from complete.

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 zero filler and front-loads the most critical operational distinction: dry-run vs. actual write, and the execute gate. Every word earns its place in terms of conciseness.

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

Completeness2/5

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

Given the tool's complexity -- 13 parameters, hidden 'items' schema, nested release-group logic, no annotations -- the description is too thin to fully support an agent invocation. It handles the most important write-or-not gate, but omits context for options like max_items, delays, fallback release groups, and expected outcom. Without adding detailed parameter explanations, the tool is under-specified.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for a large parameter set. It only clarifies 'execute' and the role of 'filterDecision=skip' within items. Most members params -- such as 'root_dir', 'max_items', 'pause_seconds', 'allowed_decisions', and release-group settings -- receive no description. Given 13 params and an opaque 'items' array, this is insufficient.

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 states a clear verb and resource: 'dry-run or add multiple anime items.' This distinguishes the tool from the singular add_anime sibling and clarifies that it is a batch operation. The dry-run/write distinction further sharpens the tool's purpose.

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 clearly states when to use this tool: for adding multiple anime items, optionally in dry-run mode. It also sets the key condition 'execute must be true for writes,' giving explicit operational advice. It does not explicitly name alternatives, but the plural intent and sibling 'add_anime' make the usage context reasonably clear.

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