Skip to main content
Glama

Copiar um componente como código

designeer_component

Extract a single component or section as clean HTML and CSS plus a rendered image, so you can compare and adapt it in your own project. Target by CSS selector or visible text.

Instructions

Extrai UM componente ou seção de uma página como HTML + CSS limpos (só o que difere do padrão do navegador, classes próprias, sem script e sem depender do site) e devolve um print só dele, pra você comparar e adaptar. Ache o alvo por 'selector' (vem do designeer_capture: structure.components[...].selector ou structure.sections[...].selector) ou por 'text' (ex: 'Download now'), opcionalmente com 'kind' pra subir até o container certo (ex: text='Pro' + kind='card' = o card de preço inteiro). Não captura :hover, animações nem ::before/::after. Use como base pra adaptar no projeto, não pra clonar marca.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "designeer_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL da página, ou path de listing do Designeer
kindNoSobe a partir do texto até esse tipo de container
saveNoSalvar o .html de prévia + print em ~/designeer-media
textNoTexto visível dentro do componente
mobileNo
selectorNoSeletor CSS do elemento (do designeer_capture)
max_nodesNoLimite de elementos copiados

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does well: it states the output shape (clean HTML/CSS plus a standalone screenshot) and the exclusions (:hover, animations, ::before/::after, scripts, site dependencies). It omits side effects such as writing files to disk when save=true, which only appears in 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph that is well ordered: what the tool extracts, how to aim it, what it returns, then its limits. Every clause carries information an agent needs, with no filler.

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

Completeness4/5

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

For a 7-parameter extraction tool with no output schema and no annotations, the description covers the return value, targeting strategy, and fidelity limits adequately. The remaining gap is that the persistence behavior of save and the cost of max_nodes are left entirely to the schema.

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

Parameters4/5

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

Schema coverage is 86%, so the baseline is 3; however, the description adds real meaning to selector (its origin path in designeer_capture output), text (a concrete example, 'Download now'), and kind (text='Pro' + kind='card' yields the whole pricing card). max_nodes, save, and mobile are covered only by the schema.

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 uses a specific verb and resource: it extracts 'UM componente ou seção' as clean HTML + CSS and returns a screenshot of only that element. It distinguishes itself from the sibling designeer_capture by naming it as the source of the selector, so the agent can tell the two apart without opening a schema.

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 clearly explains how to locate the target (selector from designeer_capture, or visible text, optionally widened with 'kind') and frames the result as a base for adapting rather than cloning a brand. It doesn't explicitly say when to prefer a sibling over this tool, e.g. for whole-page extraction, so I stopped short of a 5.

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