Skip to main content
Glama
timjrobinson

Freesound MCP Server

by timjrobinson

get_user_sounds

Retrieve audio samples uploaded by a specific Freesound user. Use this tool to access user-generated sound collections by providing their username, with optional pagination controls.

Instructions

Get sounds uploaded by a specific user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesThe username of the user
pageNoPage number (default: 1)
page_sizeNoNumber of results per page (default: 15)

Implementation Reference

  • The core handler function that performs the HTTP request to Freesound API to retrieve paginated list of sounds uploaded by a specific user.
    async getUserSounds(
      username: string,
      params?: PaginationParams
    ): Promise<PaginatedResults<Sound>> {
      const response = await this.axiosInstance.get(
        `/users/${username}/sounds/`,
        {
          params: {
            page: params?.page || 1,
            page_size: params?.page_size || 15,
          },
        }
      );
      return response.data;
    }
  • src/index.ts:146-167 (registration)
    Registers the tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_user_sounds",
      description: "Get sounds uploaded by a specific user",
      inputSchema: {
        type: "object",
        properties: {
          username: {
            type: "string",
            description: "The username of the user",
          },
          page: {
            type: "number",
            description: "Page number (default: 1)",
          },
          page_size: {
            type: "number",
            description: "Number of results per page (default: 15)",
          },
        },
        required: ["username"],
      },
    },
  • Defines the input schema for the get_user_sounds tool, specifying parameters like username (required), page, and page_size.
    inputSchema: {
      type: "object",
      properties: {
        username: {
          type: "string",
          description: "The username of the user",
        },
        page: {
          type: "number",
          description: "Page number (default: 1)",
        },
        page_size: {
          type: "number",
          description: "Number of results per page (default: 15)",
        },
      },
      required: ["username"],
    },
  • MCP server handler for CallToolRequest that dispatches to FreesoundClient.getUserSounds and formats the response.
    case "get_user_sounds": {
      const sounds = await freesoundClient.getUserSounds(
        args.username as string,
        {
          page: args.page as number | undefined,
          page_size: args.page_size as number | undefined,
        }
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(sounds, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, it doesn't address critical aspects like authentication requirements, rate limits, pagination behavior (beyond what's in the schema), error conditions, or the format/structure of returned data. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

The description is a single, clear sentence that efficiently conveys the core purpose without any wasted words. It's appropriately sized for a straightforward tool and gets directly to the point.

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 lack of annotations and output schema, the description is insufficiently complete. It doesn't cover behavioral aspects like authentication, rate limits, or data format, and while the schema handles parameters well, the overall context for using this tool effectively is missing. For a tool with three parameters and no structured safety/behavior hints, more guidance is needed.

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 schema description coverage is 100%, with all parameters clearly documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema (e.g., it doesn't explain what 'sounds' entail or provide context about username formats). This meets the baseline for when the schema does the heavy lifting.

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 clearly states the verb ('Get') and resource ('sounds uploaded by a specific user'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_user' or 'search_sounds', but the specificity of 'sounds uploaded by a specific user' provides adequate clarity for a read operation.

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 like 'get_user' (which might return user metadata) or 'search_sounds' (which might allow broader filtering). It simply states what the tool does without context about when it's appropriate or what distinguishes it from similar tools.

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