miromiro

Extract SVGs

extract_svgs

Read-onlyIdempotent

Use when the user wants a site's icons or vector logos: inline SVGs as paste-ready markup plus external .svg file URLs. Not for: raster images (use extract_assets). Returns 20 by default with long markup trimmed; pass limit (up to 200) for more and full_output=true for complete SVG code.

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 SVGs to return (default 20, 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	Return complete SVG markup instead of trimming long code. 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
`svgs`	No
`count`	No	Total SVGs 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.4/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent, open-world read (readOnlyHint/idempotentHint true, destructiveHint false), so the safety burden is lifted. The description adds genuinely useful behavior beyond that: long markup is trimmed by default, only 20 results come back unless asked, and full_output restores complete code. It does not cover caching or rate-limit behavior, and the limit/full_output defaults are partly restated from the schema.

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?

Three tight, front-loaded sentences: trigger first, exclusion second, output/defaults third. Slightly redundant with the schema on limit and full_output, which costs a bit of efficiency, but there is no filler.

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 still tells the agent the response shape (inline markup + .svg URLs) and the trimming default. Combined with annotations covering safety, this is complete for a 7-parameter extraction tool.

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 every parameter is already documented with rich guidance (fresh, render, screenshot, response_format all have detailed schema text). The description only restates the limit and full_output defaults, adding no syntax or format detail the schema lacks. Baseline 3 is appropriate 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (extract SVGs) and immediately narrows the scope to a site's icons or vector logos, plus names the output form (inline markup plus external .svg URLs). It explicitly distinguishes itself from extract_assets, so an agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a positive trigger ('when the user wants a site's icons or vector logos') and an explicit exclusion with the alternative named ('Not for: raster images (use extract_assets)'). Nothing about tool selection is left to inference.

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.