Openverse

Search Audio

search_audio

Read-onlyIdempotent

"Find royalty-free / Creative Commons / public-domain audio for [X]" / "free music / sound effects of [Y]" / "CC-licensed audio" — search Creative-Commons-licensed audio (music, sound effects, podcast clips) via Openverse. Filter by license, source. Use for video/podcast/game soundtracks that need legal reuse.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`query`	Yes
`source`	No
`license`	No
`page_size`	No
`license_type`	No

Output Schema

TableJSON Schema

Name	Required	Description
`page`	No	Current page number
`results`	No	Array of audio results
`page_size`	No	Results per page
`page_count`	No	Total number of pages
`result_count`	No	Total number of results available

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 16, 2026
- changedOutput schema / properties / results / items / properties / bit_rate / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / category / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / filesize / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / sample_rate / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / tags / items / properties / accuracy / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "ambient music"
+  },
+  {
+    "license": "by",
+    "license_type": "commercial",
+    "page": 1,
+    "query": "bird sounds"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "page": {
+      "description": "Current page number",
+      "type": "integer"
+    },
+    "page_count": {
+      "description": "Total number of pages",
+      "type": "integer"
+    },
+    "page_size": {
+      "description": "Results per page",
+      "type": "integer"
+    },
+    "result_count": {
+      "description": "Total number of results available",
+      "type": "integer"
+    },
+    "results": {
+      "description": "Array of audio results",
+      "items": {
+        "properties": {
+          "bit_rate": {
+            "description": "Bit rate in kbps",
+            "type": "integer"
+          },
+          "category": {
+            "description": "Audio category",
+            "type": "string"
+          },
+          "creator": {
+            "description": "Audio creator name",
+            "type": "string"
+          },
+          "creator_url": {
+            "description": "Creator profile URL",
+            "type": "string"
+          },
+          "download_url": {
+            "description": "Download URL",
+            "type": "string"
+          },
+          "duration": {
+            "description": "Duration in milliseconds",
+            "type": "integer"
+          },
+          "filesize": {
+            "description": "File size in bytes",
+            "type": "integer"
+          },
+          "filetype": {
+            "description": "File format",
+            "type": "string"
+          },
+          "foreign_landing_url": {
+            "description": "Original source URL",
+            "type": "string"
+          },
+          "id": {
+            "description": "Audio unique identifier",
+            "type": "string"
+          },
+          "license": {
+            "description": "License type",
+            "type": "string"
+          },
+          "license_url": {
+            "description": "License details URL",
+            "type": "string"
+          },
+          "license_version": {
+            "description": "License version",
+            "type": "string"
+          },
+          "provider": {
+            "description": "Source provider",
+            "type": "string"
+          },
+          "sample_rate": {
+            "description": "Sample rate in Hz",
+            "type": "integer"
+          },
+          "source": {
+            "description": "Source identifier",
+            "type": "string"
+          },
+          "tags": {
+            "description": "Associated tags",
+            "items": {
+              "properties": {
+                "accuracy": {
+                  "description": "Tag accuracy score",
+                  "type": "number"
+                },
+                "name": {
+                  "description": "Tag name",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Audio title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Audio URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false), lowering the bar. The description adds genuinely useful behavioral context beyond that: the backend is Openverse and results are legally reusable CC-licensed content. It does not disclose pagination or rate-limit behavior, but no contradiction exists and the annotations cover the risk profile.

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 efficient and well-ordered: example query phrasings first, then the core function, filters, and use case. The quoted examples at the start are slightly unconventional but earn their place by grounding the agent in realistic query formats. No filler or redundancy.

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

Completeness3/5

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

The core task — finding legally reusable audio — is well covered, and the output schema handles return-value documentation. However, with six parameters and zero schema coverage, the description leaves page, page_size, and license_type unexplained, so an agent cannot reliably construct non-basic queries. Adequate overall, but with a clear parameter-documentation gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for six unannotated parameters. It only names 'Filter by license, source', covering two of six, and the overall purpose implies query. The page, page_size, and license_type parameters remain completely unexplained in both schema and description, so an agent must guess their semantics and accepted values.

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 states a specific verb ('search'), a precise resource (Creative-Commons-licensed audio via Openverse), and the content scope (music, sound effects, podcast clips). It clearly differentiates from siblings like search_images, get_audio, and audio_related by emphasizing the CC-license constraint, which is the tool's defining characteristic.

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 gives a clear use context: 'Use for video/podcast/game soundtracks that need legal reuse,' which tells an agent when this tool is appropriate. It does not, however, explicitly name alternatives or state when not to use it (e.g., get_audio for fetching a specific file, audio_related for recommendations), leaving some routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Openverse tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.