Skip to main content
Glama
rollecode

Trakt MCP server

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_sync_collection_shows

Read-onlyIdempotent

Retrieve shows from your Trakt sync collection. Supports pagination, extended metadata, and availability filtering.

Instructions

Get show collection.

GET /sync/collection/shows

Args: extended: Extended information to include in the response. available_on: Query parameter. page: The page number to retrieve limit: The number of items per page. Defaults and maximums vary by endpoint. When pagination parameters are omitted, a low default limit is applied (often 10). When a limit is provided, it is capped at the endpoint maximum (often 250); higher values are clamped rather than rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNo
extendedNo
available_onNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.3
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Limit"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Page"
+}
  2. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior. The description does add real pagination behavior (low default limit ~10, cap ~250, values clamped rather than rejected), which is useful context beyond the schema. It does not say whose collection is returned or how auth is scoped.

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

Conciseness3/5

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

The layout (one-line purpose, endpoint, Args list) is readable and front-loaded, but the Args block restates parameter names with little added value and the GET path duplicates information the agent already has from the tool name.

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?

An output schema exists, so return values need not be described. Pagination is reasonably covered, but the definition omits whose collection this is, what 'extended' actually returns, and what 'available_on' filters by—gaps that matter for a four-parameter read endpoint.

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 carry parameter meaning, and it largely fails: 'extended: Extended information to include in the response' is tautological and 'available_on: Query parameter' is a placeholder with no semantics. Only page and limit gain any real explanation via the pagination note, leaving two of four parameters effectively undocumented.

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

Purpose3/5

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

The description says 'Get show collection' with the endpoint path, which signals a read of the user's synced show collection. However, it does not distinguish this tool from close siblings like list_sync_collection_movies, list_sync_collection_minimal_shows, or get_sync_collection_by_type, so an agent must infer the difference from the name alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite information, and no mention of alternatives among the many sibling collection endpoints. The only hint is the endpoint path, which is not usage guidance.

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