Skip to main content
Glama

trash_list_profiles

List quality profiles from TRaSH Guides for Radarr or Sonarr, showing recommended profiles for 1080p, 4K, Remux, and more.

Instructions

List available TRaSH Guides quality profiles for Radarr or Sonarr. Shows recommended profiles for different use cases (1080p, 4K, Remux, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesWhich service to get profiles for

Implementation Reference

  • src/index.ts:756-769 (registration)
    Tool registration: defines the 'trash_list_profiles' tool with schema requiring a 'service' enum parameter (radarr or sonarr)
      name: "trash_list_profiles",
      description: "List available TRaSH Guides quality profiles for Radarr or Sonarr. Shows recommended profiles for different use cases (1080p, 4K, Remux, etc.)",
      inputSchema: {
        type: "object" as const,
        properties: {
          service: {
            type: "string",
            enum: ["radarr", "sonarr"],
            description: "Which service to get profiles for",
          },
        },
        required: ["service"],
      },
    },
  • Handler: the switch case that executes the 'trash_list_profiles' tool logic by calling trashClient.listProfiles(service) and returning the list of profile names with descriptions
    case "trash_list_profiles": {
      const service = (args as { service: TrashService }).service;
      const profiles = await trashClient.listProfiles(service);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            service,
            count: profiles.length,
            profiles: profiles.map(p => ({
              name: p.name,
              description: p.description?.replace(/<br>/g, ' ') || 'No description',
            })),
            usage: "Use trash_get_profile to see full details for a specific profile",
          }, null, 2),
        }],
      };
    }
  • Helper: TrashClient.listProfiles() - fetches quality profile list from the TRaSH Guides GitHub repo, with caching. Returns profile names and descriptions.
    async listProfiles(service: TrashService): Promise<{ name: string; description?: string }[]> {
      // Check cache
      const cached = cache.getProfileList(service);
      if (cached) {
        // Fetch details for each
        const profiles = await Promise.all(
          cached.map(name => this.getProfile(service, name))
        );
        return profiles.filter((p): p is TrashQualityProfile => p !== null).map(p => ({
          name: p.name,
          description: p.trash_description,
        }));
      }
    
      // Fetch list from GitHub
      const profileNames = await listGitHubDir(`${service}/quality-profiles`);
      cache.setProfileList(service, profileNames);
    
      // Fetch details
      const profiles = await Promise.all(
        profileNames.map(name => this.getProfile(service, name))
      );
      return profiles.filter((p): p is TrashQualityProfile => p !== null).map(p => ({
        name: p.name,
        description: p.trash_description,
      }));
    }
  • Helper: TrashClient.getProfile() - fetches a specific quality profile JSON from TRaSH Guides repo, used by listProfiles to get details for each profile
    async getProfile(service: TrashService, profileName: string): Promise<TrashQualityProfile | null> {
      const key = `${service}/${profileName}`;
      const cached = cache.getProfile(key);
      if (cached) return cached;
    
      try {
        const profile = await fetchJSON<TrashQualityProfile>(
          `${TRASH_BASE_URL}/${service}/quality-profiles/${profileName}.json`
        );
        cache.setProfile(key, profile);
        return profile;
      } catch {
        return null;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as read-only nature, caching, or any side effects. It simply states the action without transparency.

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?

Two concise sentences with no fluff. The description is front-loaded with the key action and resource.

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

Completeness4/5

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

For a simple list tool with one parameter and no output schema, the description is mostly complete. It mentions the type of profiles and use cases, but could elaborate on return format or fields included.

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 coverage is 100% and the parameter is described in schema. The description adds context about quality profiles and use cases but does not add new semantic information beyond the schema.

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 clearly states the verb 'List' and the resource 'TRaSH Guides quality profiles', specifies the two services (Radarr/Sonarr), and mentions use cases, distinguishing it from sibling tools like trash_compare_profile or trash_get_profile.

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 implies usage for selecting profiles by use case, but does not explicitly state when to choose this over alternatives like trash_get_profile or trash_compare_profile. No exclusions or context are provided.

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/aplaceforallmystuff/mcp-arr'

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