Skip to main content
Glama

Remove Logo

remove_logo
DestructiveIdempotent

Remove the uploaded logo and go back to the text logotype (the business name in the site's heading font — every site's default, a legitimate finished look). The favicon falls back to the automatic monogram. The user's photo-library image is left untouched (this call deletes nothing), so a JPEG/PNG/WebP logo can be set again later with set_logo. Already on the text logotype? The call reports that and changes nothing.

Annotations: read-only=false, destructive=true, idempotent=true, open-world=false. Why: Clears the logo from the DRAFT (an overwrite, 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>"
    },
    "name": "remove_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses concrete consequences: the favicon falls back to the automatic monogram, the photo-library image survives, and a no-op state is reported without changes. It also pre-empts the apparent tension with destructiveHint=true by clarifying that 'deletes nothing' refers to the source asset while the draft logo is overwritten, and the annotation rationale confirms this reading.

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?

The description leads with the action and outcome, and each sentence adds a distinct fact about the resulting state. It's somewhat dense with parentheticals and em-dashes, but no sentence is 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?

It is thorough for a one-parameter mutation with no output schema: it covers the outcome, the side effects on favicon and photo library, idempotent behavior, and draft-vs-live scope. Nothing an agent needs in order to call it correctly 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?

There is a single required site_id with 0% schema description coverage, so the description would need to compensate for that gap, yet it never mentions site_id at all. The schema's UUID format and pattern still make the parameter legible, which keeps this at a minimum-viable 3 rather than lower.

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 and resource ('Remove the uploaded logo') and explicitly names the resulting state ('go back to the text logotype'), which cleanly distinguishes it from the sibling set_logo. An agent can tell it apart from set_logo without inspecting 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 Guidelines4/5

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

It gives clear context for when this applies and names set_logo as the counterpart for re-setting a JPEG/PNG/WebP logo later. It also handles the 'already on the text logotype' case, but it never states an explicit when-not condition or prerequisites such as draft ownership, leaving some inference to the agent.

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.