Skip to main content
Glama

sonarr_refresh_series

Trigger a metadata refresh for a specified Sonarr series to update its details from source data. Use when series metadata is stale or missing.

Instructions

Trigger a metadata refresh for a specific series in Sonarr

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "seriesId": "<seriesId>"
    },
    "name": "sonarr_refresh_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYesSeries ID to refresh

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / seriesId / minimum
      Added value: +1
    • changedInput schema / properties / seriesId / type
      Previous value: -"number"New value: +"integer"
  2. Addedv1.6.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the refresh is metadata-scoped and limited to one series, but does not say whether the call is asynchronous (queues a command) or whether it returns after completion — a meaningful gap for a non-idempotent command-style tool.

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

Conciseness4/5

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

One front-loaded sentence with zero filler; the verb and target are immediately visible. Minor redundancy in 'in Sonarr' given the tool name already encodes the product.

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?

For a simple one-parameter tool with no output schema this covers the essentials, but it omits whether the refresh is queued asynchronously, what the response indicates, and what 'metadata' actually covers (episodes, images, titles). An agent can call it but cannot predict the result.

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 there is a single required integer parameter already documented as 'Series ID to refresh'. The description adds no format, sourcing, or lookup guidance (e.g., where to obtain the ID) beyond restating the scope, so baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb and resource ('Trigger a metadata refresh') scoped to 'a specific series', which clearly separates it from siblings like sonarr_get_series or sonarr_add_series. It is clear what the tool does, though it never names a sibling to contrast against.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for refreshing stale metadata on an existing series, but the description gives no explicit when-to-use, when-not-to-use, or prerequisites (e.g., that the series must already exist in the library). No alternative is mentioned.

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

Deploy Server

Other Tools