Skip to main content
Glama

trakt_get_sync_status

Check the status of ongoing Plex to Trakt sync operations to see if they are active or complete.

Instructions

Check status of ongoing sync operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler for trakt_get_sync_status. Calls syncEngine.getSyncStatus() and returns syncInProgress, syncId, and a human-readable message.
    async traktGetSyncStatus(): Promise<Record<string, unknown>> {
      if (!this.isInitialized) {
        return {
          syncInProgress: false,
          error: 'Trakt client not initialized'
        };
      }
    
      const status = this.syncEngine.getSyncStatus();
      
      return {
        syncInProgress: status.inProgress,
        syncId: status.syncId,
        message: status.inProgress ? 'Sync in progress' : 'No active sync'
      };
    }
  • Schema definition for trakt_get_sync_status with name, description, and empty inputSchema (no parameters needed).
    {
      name: "trakt_get_sync_status",
      description: "Check status of ongoing sync operations",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • Registration of trakt_get_sync_status in the tool registry, wiring it to traktFunctions.traktGetSyncStatus().
    registry.register("trakt_get_sync_status", () =>
      traktFunctions.traktGetSyncStatus().then(wrapResponse)
    );
  • getSyncStatus() helper on TraktSyncEngine that returns { inProgress, syncId, startedAt } from the engine's internal state.
    getSyncStatus(): { inProgress: boolean; syncId: string | null; startedAt?: Date } {
      return {
        inProgress: this.syncInProgress,
        syncId: this.currentSyncId
      };
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits like whether the tool is read-only, idempotent, or what side effects exist. The description adds no behavioral context beyond the name.

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?

The description is a single 4-word sentence, very concise. While it could include a brief note on return format, for a parameterless tool this level of conciseness is acceptable.

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?

The description covers the basic purpose but lacks detail about the status output (e.g., possible values, meaning). Without an output schema, the agent may need more context on what the status response contains.

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

Parameters4/5

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

The input schema has no parameters, so schema description coverage is 100% trivially. For zero parameters, the baseline is 4. The description does not add parameter meaning but also does not need to, as there are none.

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 'Check status of ongoing sync operations' clearly identifies the tool's function with a specific verb and resource. It differentiates from sibling tools like trakt_sync_from_trakt and trakt_sync_to_trakt, which initiate sync rather than check status.

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?

The description provides no guidance on when to use this tool versus alternatives. Given siblings that perform sync actions, an agent lacks context on when to check status versus initiate sync, such as checking after initiating a sync.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/niavasha/plex-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server