Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

set_creator_credit

Destructive

Saves creator credit, external links, and optional license terms for an account or a specific design, with show, hide, or default credit settings.

Instructions

Save Pro+ creator credit, external links, and optional license terms, for the account or for one design (design_id with design_credit = "show", "hide" or "default").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_creator_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksNoExternal links, each ``{"label": ..., "url": ...}`` with a direct HTTPS URL, at most 5. Supplied, it replaces the saved list (``[]`` clears it); omitted, the saved list is kept.
handleNoThe account's username. Required for an account-level save; pass the current one to keep it. Leave it out when setting one design's credit.
design_idNoOne design whose credit is set. Give it with ``design_credit`` and no other settings on the same call.
design_creditNoThe credit choice for ``design_id``: ``"show"``, ``"hide"`` or ``"default"`` (follow the account setting).
default_licenseNoThe license attached to future files: ``{"name": ..., "terms_text": ...}`` or ``{"name": ..., "terms_url": ...}`` with a direct HTTPS URL. Omitted, the saved license is kept; ``{}`` clears it.
show_on_artifactsNoWhether files Kiln makes name the creator. Omitted, the saved setting is kept.
show_license_on_artifactsNoWhether files Kiln makes carry the license. Omitted, the saved setting is kept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating, potentially lossy operation. The description confirms the save semantics and adds the Pro+ prerequisite, but it does not itself warn that supplying links replaces the saved list or that an empty license object clears stored terms — that information lives only in the schema property text.

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?

A single sentence that front-loads the verb and the set of fields, with the mode switch relegated to a trailing parenthetical. There is no filler and nothing is buried.

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-optional-parameter mutation tool with nested objects and no output schema, the description covers the main structural question (account vs design scope) and the tier requirement. The remaining gap — merge vs replace semantics for omitted fields — is fully covered by the per-property schema text, so the definition is complete enough to call correctly.

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 links and default_license objects is already documented. The description adds only a light framing of design_id/design_credit as the per-design mode and the allowed credit values, which the schema also lists. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description gives a specific verb ("Save") and names the concrete resources: Pro+ creator credit, external links, and license terms. It also distinguishes the two scopes (account-level vs a single design via design_id/design_credit), which is the key ambiguity an agent would otherwise have to resolve from the schema alone.

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 establishes the two usage modes and the fact that the per-design path is selected by pairing design_id with design_credit ("show", "hide", "default"). The "Pro+" qualifier signals a tier prerequisite. It stops short of naming the read counterpart (get_creator_credit) or stating that the two modes cannot be mixed, but the context needed to pick a mode is present.

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

Deploy Server

Other Tools