Skip to main content
Glama

Edit thumbnail text and image layers

edit_thumbnail_layers
Idempotent

On Editable (layered) runs, change text layers (content, anchor top/bottom, typography preset, fill hex, size px, position) or image layers (scale, corner anchor, position) by index from get_thumbnail. Null clears an override back to the default. No image model call and no edit allowance. Adds a new version. Poll get_thumbnail.

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": {
      "runId": "<runId>",
      "rank": "<rank>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "edit_thumbnail_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
rankYes
runIdYes
textLayersNo
assetLayersNo
idempotencyKeyYes

Output Schema

NameRequiredDescriptionDefault
rankYes
runIdYes
editIdYes
statusYes
pollAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (idempotent, non-destructive, closed-world), the description discloses several things they cannot: null clears an override to default, a new version is created, there is no image model call and no edit allowance consumed, and progress is observed by polling get_thumbnail. It stops short of error behavior or what happens on an out-of-range index/rank.

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?

Extremely dense with no filler: the main operation is front-loaded, followed by short, high-value sentences on null semantics, cost, versioning, and polling. Every clause carries information an agent would otherwise have to guess.

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 mutation tool with an output schema and rich annotations, the description covers side effects, cost, and the async retrieval path, which is most of what is needed. The main hole is the meaning of the required 'rank' parameter and how indices relate to it, which the schema cannot convey at 0% description coverage.

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 description coverage is 0%, so the description must carry the load, and it does for the two nested arrays: it enumerates text-layer fields (content, anchor top/bottom, preset, fill hex, size px, position), image-layer fields (scale, corner anchor, position), and explains the null-clears semantics. runId, rank, and idempotencyKey are left uninterpreted, and 'rank' in particular (1-24, required) is never explained.

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 precise verb-plus-resource ('change text layers ... or image layers') scoped to 'Editable (layered) runs', and names the exact fields each layer type accepts. It also implicitly separates itself from the sibling edit_thumbnail by noting 'No image model call', so an agent can tell which of the two edit paths applies.

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?

The precondition 'On Editable (layered) runs' is an explicit gate that tells the agent when this tool applies, and 'by index from get_thumbnail' says where the index values come from. It ends with 'Poll get_thumbnail', giving the follow-up step. It does not explicitly name the alternative for non-layered runs, but the scoping constraint makes the choice inferable.

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.

Resources