Assign or change a language profile for a specific series in Bazarr by providing the series ID and profile ID, solving subtitle language mismatch issues.
Update specific series languages profile.
POST /api/series
Args: seriesid: Sonarr series ID profileid: Languages profile(s) ID or "none"
| Name | Required | Description | Default |
|---|---|---|---|
| seriesid | No | ||
| profileid | No |
| 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?
Beyond the annotations, the description only says 'Update', which does not disclose side effects, whether the previous profile is replaced, or any authentication prerequisites. It adds no behavioral context to the existing idempotentHint/readOnlyHint annotations.
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 short and front-loaded, with a clear one-sentence overview followed by a compact args list. The endpoint line adds minor context but is not waste.
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?
With an output schema and simple parameters, the core call information is mostly present, and the parameter semantics are documented. However, the missing usage guidance and the create/update ambiguity leave an agent without enough context to confidently select and invoke the tool.
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 coverage is 0%, but the description compensates by explaining that seriesid is the Sonarr series ID and profileid is the language profile ID(s) or the sentinel 'none'. This gives crucial meaning not available in the schema.
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 states a specific action ('Update specific series languages profile') on a specific resource, so an agent can understand the operation. However, it does not differentiate from siblings such as patch_series or create_series, and the tool name 'create_series' conflicts with the update semantics.
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 about when to use this tool versus alternatives like patch_series or create_series, or when the 'none' profile value is appropriate. The context is limited to raw parameters, leaving selection to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.