miromiro

Extract audio

extract_audio

Read-onlyIdempotent

Use when the user wants the audio files on a page: / files, og:audio, podcast enclosures and download links, each tagged by source. A URL that is itself an audio file comes back as the single result (source file). If a JavaScript player mounts the audio at runtime, call again with render=true (+5 credits). Returns up to 40 by default; pass limit (up to 200) for more.

Input Schema

Name	Required	Description
`url`	Yes	The website URL
`fresh`	No	Skip the 24-hour cache and re-extract the live page - use when the site just changed and a cached result would be stale. Charged normally; the fresh result replaces the cached copy.
`limit`	No	Max audio files to return (default 40, up to 200).
`render`	No	Force a real browser so the page's JavaScript runs before it is read. Slower, and adds 5 credits. Usually not needed: when the plain read comes back as a JavaScript app shell or the site refuses it (401/403/406) or timed out, the server already re-runs the page in a browser by itself at no extra cost, and usage.autoRender says so. Pass it for images, videos or Lottie that only load on scroll, with screenshot=true, or when a result is still thin after that automatic pass. If a 403 says the browser was refused too, the site cannot be extracted - do not retry. extract_code always runs in a real browser at no extra cost, so render=true is not needed there (only together with screenshot=true). On extract_design_tokens, render=true only permits the browser: the plain read still runs first, and the 5 credits are charged only if the browser was actually needed.
`screenshot`	No	Requires render=true. Adds a screenshot field to the result: a public URL of a capture of the page (live 7 days), taken by the same browser that rendered it. Pass true for the 1440x900 viewport or 'full' for the entire page height. No extra credits beyond the render surcharge. Useful for showing the user what the extracted site looks like.
`full_output`	No	Skip long-string trimming. Responses still cap at ~100KB total.
`response_format`	No	How much to return. 'concise' keeps lists to 10 entries and strings short - right for a summary or a chat answer. 'detailed' returns everything the tool has (same as limit=200 + full_output=true). Omit for the default, which fits a typical chat context. The generated code is never trimmed in any mode.

Output Schema

Name	Required	Description
`url`	Yes
`note`	No	Coverage caveat: only audio declared in the initial HTML is found - use render=true for JS-mounted players
`audio`	No
`count`	No	Total audio files found (before any trimming)
`usage`	No	Credit usage for the authed key (spent, remaining, monthly limit).
`truncation_note`	No	Present when the result was trimmed to fit chat context - says what was dropped and how to get more (limit / full_output arguments, or the REST API).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds real behavioral context beyond them: per-source tagging of results, the 40-item default cap, and the +5 credit surcharge for render=true. It stops short of describing failure modes or rate limits, which the schema's render note partially covers instead.

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?

Front-loaded with the trigger, then the special cases and limits in four tight sentences with no filler. A minor redundancy with the schema on the limit/render details keeps it from a 5.

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

Completeness5/5

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

An output schema exists so return values need no explanation. The description covers the edge case where the URL is itself an audio file, the JS-runtime case, the credit cost, and pagination limits, which is everything an agent needs to call it correctly.

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%, so baseline is 3. The description restates limit ('up to 200') and the render surcharge, both of which the schema already documents in more depth, so it adds little parameter meaning of its own.

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+resource ('the audio files on a page') and enumerates exactly what counts as audio: <audio>/<source>, og:audio, podcast enclosures, download links. This distinguishes it cleanly from sibling extractors like extract_videos, extract_svgs and extract_fonts.

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?

It gives an explicit trigger ('Use when the user wants the audio files on a page') and a follow-up condition ('If a JavaScript player mounts the audio at runtime, call again with render=true'). It does not, however, name the sibling tools to prefer for non-audio media, so the routing guidance is clear but not complete.

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

All miromiro tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.