Skip to main content
Glama

Marke von der Website übernehmen

brand_import_from_website

Liest eine öffentliche Firmenwebsite aus und schlägt daraus ein Briefkopf-Design vor: Markenfarben, Hausschriftzuordnung, Logo-Kandidaten und Firmendaten aus dem Impressum. Die gefundenen Logos landen als Design-Assets im Konto und sind sofort verwendbar. Das Ergebnis ist ein Vorschlag zur Abstimmung mit der Kundin oder dem Kunden; übernommen wird die Marke erst durch einen anschließenden Aufruf von brand_kit_save mit brandingOwnershipConfirmed. Technischer Tool-Name: brand_import_from_website. EN: Reads a public company website and proposes a letterhead design from it: brand colours, a mapped house typeface, logo candidates and company details from the imprint. Found logos are stored as design assets in the account and are usable right away. The result is a proposal to review with the customer; the brand is adopted by a following brand_kit_save call carrying brandingOwnershipConfirmed. Technical tool name: brand_import_from_website.

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": {
      "websiteUrl": "<websiteUrl>"
    },
    "name": "brand_import_from_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasoningNoKurze Begründung für das Audit-Protokoll. EN: Short rationale for the audit log.
websiteUrlYesÖffentliche Adresse der Firmenwebsite, zum Beispiel https://beispiel.de. EN: Public company website address.
maxLogoCandidatesNoWie viele Logo-Kandidaten heruntergeladen und gespeichert werden. Standard 3. EN: How many logo candidates get downloaded and stored. Default 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / reasoning / description
      Previous value: -"Kurze Begruendung fuer das Audit-Protokoll. EN: Short rationale for the audit log."New value: +"Kurze Begründung für das Audit-Protokoll. EN: Short rationale for the audit log."
    • changedInput schema / properties / websiteUrl / description
      Previous value: -"Oeffentliche Adresse der Firmenwebsite, zum Beispiel https://beispiel.de. EN: Public company website address."New value: +"Öffentliche Adresse der Firmenwebsite, zum Beispiel https://beispiel.de. EN: Public company website address."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds significant context beyond the annotations: logos are persisted as design assets in the account and are immediately usable (a durable side effect, even though destructiveHint is false), the call performs an outbound fetch of a public site, and adoption is deliberately deferred to a later call. This is exactly the non-obvious write/network behaviour an agent needs to know before invoking it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The content is front-loaded and well ordered (what it does, what happens, what to do next), but the entire text is duplicated in German and English, roughly doubling length without adding information. A one-language version would be considerably tighter.

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?

No output schema exists, yet the description fully describes the return: proposed brand colours, a mapped typeface, logo candidates, and imprint company data, plus the fact that it is a proposal rather than an applied state. Nothing an agent needs to call this correctly or interpret the result is missing.

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 all three parameters are already documented in-schema. The description mentions the kinds of data extracted and that logos get stored, but adds no new constraints, defaults, or format guidance beyond what the schema states. Baseline 3 applies.

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 and resource: reads a public company website and proposes a letterhead design, enumerating the concrete outputs (brand colours, house typeface, logo candidates, imprint data). An agent understands exactly what it gets back without opening the 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?

Explicitly frames the result as a proposal for customer review and names the follow-up call (brand_kit_save with brandingOwnershipConfirmed) that actually adopts the brand, which is genuinely useful routing. However, it never distinguishes itself from the sibling tool brand_setup_from_website, which sounds near-identical in purpose — a notable gap given the alternatives available.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.