Skip to main content
Glama
timjrobinson

Freesound MCP Server

by timjrobinson

get_pack_sounds

Retrieve audio samples from a specific sound pack on Freesound.org using the pack ID. Specify page number and results per page to navigate large collections.

Instructions

Get sounds from a specific pack

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pack_idYesThe ID of the pack
pageNoPage number (default: 1)
page_sizeNoNumber of results per page (default: 15)

Implementation Reference

  • MCP CallToolRequest handler case for 'get_pack_sounds': parses arguments, calls FreesoundClient.getPackSounds, and returns results as JSON-formatted text content.
    case "get_pack_sounds": {
      const sounds = await freesoundClient.getPackSounds(
        args.pack_id as number,
        {
          page: args.page as number | undefined,
          page_size: args.page_size as number | undefined,
        }
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(sounds, null, 2),
          },
        ],
      };
    }
  • src/index.ts:182-203 (registration)
    Registration of the 'get_pack_sounds' tool in the ListTools response, defining its name, description, and input schema.
    {
      name: "get_pack_sounds",
      description: "Get sounds from a specific pack",
      inputSchema: {
        type: "object",
        properties: {
          pack_id: {
            type: "number",
            description: "The ID of the pack",
          },
          page: {
            type: "number",
            description: "Page number (default: 1)",
          },
          page_size: {
            type: "number",
            description: "Number of results per page (default: 15)",
          },
        },
        required: ["pack_id"],
      },
    },
  • Helper method in FreesoundClient that performs the API request to retrieve paginated list of sounds from a specific pack.
    async getPackSounds(
      packId: number,
      params?: PaginationParams
    ): Promise<PaginatedResults<Sound>> {
      const response = await this.axiosInstance.get(`/packs/${packId}/sounds/`, {
        params: {
          page: params?.page || 1,
          page_size: params?.page_size || 15,
        },
      });
      return response.data;
    }
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 only states the basic action without disclosing behavioral traits such as pagination behavior (implied by parameters but not described), rate limits, authentication needs, or what the output contains (e.g., sound metadata or files). This leaves significant gaps for a tool with pagination parameters.

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, efficient sentence that directly states the tool's purpose without unnecessary words. However, it could be more front-loaded with key details (e.g., pagination) to improve structure, but it earns high marks for brevity and clarity in its limited scope.

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

Completeness2/5

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

Given the tool's complexity (3 parameters including pagination) and lack of annotations and output schema, the description is incomplete. It doesn't address what the tool returns (e.g., sound objects, metadata), how pagination works, or error conditions, making it inadequate for an agent to use effectively without additional context.

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?

The input schema has 100% description coverage, providing clear details for all parameters (pack_id, page, page_size). The description adds no additional meaning beyond the schema, as it doesn't explain parameter interactions or usage context. With high schema coverage, the baseline score of 3 is appropriate.

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 'Get sounds from a specific pack' clearly states the action (get) and resource (sounds from a pack), but it's vague about scope and doesn't distinguish from siblings like 'get_sound' or 'get_user_sounds'. It lacks specificity about what 'sounds' means (e.g., metadata, files, or listings).

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. It doesn't mention siblings like 'get_sound' (for individual sounds) or 'search_sounds' (for broader queries), leaving the agent to infer usage from context without explicit direction.

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/timjrobinson/FreesoundMCPServer'

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