Skip to main content
Glama

Set Logo

set_logo
DestructiveIdempotent

Make an image the site's logo (header, footer AND favicon — the favicon pair is generated automatically, transparency is detected, and the logo's dominant brand colors come back as suggested_colors). image_url must be one of THIS site's own images: something the user uploaded via request_image_upload + finalize_image_upload, or an existing photo from list_site_photos — any other URL is rejected. A solid-background (non-transparent) image works but looks best as a transparent PNG; the response says which was detected. suggested_colors are ONLY suggestions — offer them to the user ("want the site to match your logo?") and apply via update_design if they say yes; never apply unprompted. The response includes a fresh preview_url — share that link.

Annotations: read-only=false, destructive=true, idempotent=true, open-world=false. Why: Overwrites the draft's logo with the given image — non-additive, so destructive by the MCP definition; idempotent; closed-world. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

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": {
      "site_id": "<site_id>",
      "image_url": "<image_url>"
    },
    "name": "set_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes
image_urlYesURL of an image in THIS site's photo library (from finalize_image_upload or list_site_photos)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructive/idempotent/closed-world, and the description goes well past them by explaining the draft-vs-live distinction (live site changes only on publish_site), automatic favicon generation, transparency detection, and the shape of the returned data (suggested_colors, preview_url). This is exactly the context annotations cannot carry.

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 action, then constraints, then response-guidance — a sensible order with no filler sentences. It is dense and parenthesis-heavy, and could be split slightly for readability, but nearly every clause carries operational meaning.

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 still tells the agent what comes back (suggested_colors, transparency detection, fresh preview_url to share) and how to act on it. Combined with the valid-source rule for the image, an agent has everything needed to invoke this correctly on the first try.

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 50% and the description compensates well for image_url by spelling out accepted sources and the rejection rule for foreign URLs, which the schema description only hints at. site_id is left unaddressed, but its role is self-evident from the surrounding tool set.

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?

Specific verb+resource: "Make an image the site's logo" immediately scoped to header, footer, and favicon. It is unmistakably distinct from siblings like remove_logo, update_design, or the upload tools, and the scope expansion (favicon auto-generated) is stated up front.

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?

Explicitly constrains the input source: the URL must come from request_image_upload + finalize_image_upload or list_site_photos, and any other URL is rejected — naming the sibling tools that produce valid inputs. It also gives behavioral guidance for the follow-up: offer suggested_colors to the user and apply only via update_design if they agree, never unprompted.

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.