Skip to main content
Glama
Sign In

Layerre

by com.layerre
OverviewDiscussionsAdmin

Update template

layerre_update_template
Idempotent

Update template properties like name, dimensions, background color, or tags. Tags use replace semantics — pass the full desired tag list. Changing dimensions or background will regenerate the preview in the background.

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": {
      "template_id": "<template_id>"
    },
    "name": "layerre_update_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew template name
tagsNoReplace all tags on this template. Pass [] to clear all tags. Omit to leave tags unchanged.
widthNoNew template width in pixels
heightNoNew template height in pixels
template_idYesThe UUID of the template to update
background_colorNoBackground color of the first page (page 0) in hex format (#RRGGBB)
page_backgroundsNoPer-page background colors to merge, keyed by page index string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that: tags use replace semantics (not append), and changing dimensions or background triggers a background preview regeneration — a non-obvious side effect an agent must know about. It stops short of covering permissions or failure modes.

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?

Two tightly written sentences with zero padding. The primary capability comes first, followed by the two behavioral caveats that matter most (tag replacement and async preview regeneration).

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 partial-update tool with a nested object and no output schema, the description covers the mutation semantics and the notable async side effect. It could say more about what the call returns (since there is no output schema) and confirm that omitted fields are left unchanged, but the essentials are present.

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 every parameter including the nested page_backgrounds map is already documented in the schema. The description restates the tag replace semantics and mentions the regeneration trigger but adds no format or merge details beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Update template") plus the concrete property families it can change (name, dimensions, background color, tags). This clearly separates it from layerre_get_template, layerre_list_templates, and layerre_create_template, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by the verb "Update" and the required template_id — an agent can infer this is for modifying an existing template rather than creating one. There is no explicit statement of when to prefer this over layerre_update_layer or layerre_create_variant, and no prerequisites (permissions, template existence) are given.

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

All Layerre toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources