Skip to main content
Glama

browse_category

Browse sounds by category on myinstants.com to find meme sounds, sound effects, and viral audio clips for use in AI agent interactions.

Instructions

Browse sounds by category on myinstants.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesCategory name: anime & manga, games, memes, movies, music, politics, pranks, reactions, sound effects, sports, television, tiktok trends, viral, whatsapp audios

Implementation Reference

  • The 'browse_category' tool is registered and implemented in server.js, using the 'category' function to fetch sounds by category.
    server.tool(
      "browse_category",
      "Browse sounds by category on myinstants.com.",
      { category: z.string().describe(`Category name: ${CATEGORIES.join(", ")}`) },
      async ({ category: cat }) => {
        const match = CATEGORIES.find(c => c.toLowerCase() === cat.toLowerCase()) || cat;
        const results = await category(match);
        if (!results.length) return { content: [{ type: "text", text: `No sounds in category "${cat}"` }] };
        return { content: [{ type: "text", text: `**${match}:**\n` + results.slice(0, 20).map((r, i) => `${i + 1}. ${r.name} → \`${r.slug}\``).join("\n") }] };
      }
    );
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. It states what the tool does but lacks details on permissions, rate limits, pagination, or what the output looks like (e.g., list of sounds with metadata). This is a significant gap for a tool with no annotations.

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, efficient sentence with no wasted words. It is front-loaded with the core purpose, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., sound listings, links, metadata) or behavioral aspects like error handling. For a tool with such minimal structured data, more context 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?

Schema description coverage is 100%, with the parameter 'category' fully documented in the schema (including allowed values). The description adds no additional meaning beyond implying category-based browsing, so it meets the baseline of 3 where 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 action ('browse') and resource ('sounds by category') with the specific domain 'myinstants.com'. It distinguishes from 'play_sound' (which plays rather than browses) and 'search_sounds' (which searches rather than browses by category), though it doesn't explicitly mention these distinctions.

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?

No explicit guidance on when to use this tool versus alternatives like 'search_sounds' is provided. The description implies usage for category-based browsing but doesn't specify scenarios or exclusions, leaving the agent to infer context.

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/austenstone/myinstants-mcp'

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