Skip to main content
Glama

search_sounds

Search myinstants.com for meme sounds and sound effects to play through your speakers, enhancing interactions with reactive audio.

Instructions

Search myinstants.com for sound buttons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query

Implementation Reference

  • The handler function for the 'search_sounds' tool, which takes a query, calls the 'search' helper, and returns the formatted text results.
    async ({ query }) => {
      const results = await search(query);
      if (!results.length) return { content: [{ type: "text", text: `No sounds found for "${query}"` }] };
      return { content: [{ type: "text", text: results.slice(0, 20).map((r, i) => `${i + 1}. ${r.name} → \`${r.slug}\``).join("\n") }] };
    }
  • server.js:309-318 (registration)
    Tool registration for 'search_sounds' using the MCP server instance.
    server.tool(
      "search_sounds",
      "Search myinstants.com for sound buttons.",
      { query: z.string().describe("Search query") },
      async ({ query }) => {
        const results = await search(query);
        if (!results.length) return { content: [{ type: "text", text: `No sounds found for "${query}"` }] };
        return { content: [{ type: "text", text: results.slice(0, 20).map((r, i) => `${i + 1}. ${r.name} → \`${r.slug}\``).join("\n") }] };
      }
    );
  • The 'search' helper function that performs the web request to search for sounds.
    async function search(query) {
      return parseResults(await httpGet(`${BASE}/en/search/?name=${encodeURIComponent(query)}`));
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't describe what the search returns (sound files, metadata, links), whether results are paginated, rate limits, authentication requirements, or error conditions. 'Search' implies read-only behavior, but this isn't explicitly stated.

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 extremely concise - a single sentence with zero wasted words. It's front-loaded with the core functionality and uses straightforward language. Every word earns its place in communicating the essential purpose.

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?

For a search tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what kind of results to expect (sound files, metadata, URLs), how results are structured, or any behavioral aspects like pagination or error handling. The agent would be operating with significant uncertainty about the tool's behavior.

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 the single 'query' parameter well-documented, so the description doesn't need to compensate. The description adds no additional parameter semantics beyond what's in the schema, which is acceptable given the comprehensive schema documentation.

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 ('Search') and target resource ('myinstants.com for sound buttons'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'browse_category' or 'play_sound' - a search tool could potentially overlap with browsing functionality without clearer boundaries.

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 about when to use this tool versus alternatives like 'browse_category' or 'play_sound'. There's no mention of prerequisites, appropriate contexts, or limitations that would help an agent choose between these related sound-related 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/austenstone/myinstants-mcp'

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