Skip to main content
Glama

Upload Brand Font

upload_brand_font

Stage a single-use custom font for a brand edit. Returns font_asset_id, family, format, weight, variable, and expires_at. The asset expires after 24 hours, and the consuming edit must finish preparing before expires_at. The asset is deleted when the candidate is stored, preparation fails, or the work becomes stale. Upload it again for a later edit.

Pass either a public TTF, OTF, WOFF, or WOFF2 URL, or a completed temporary upload. For a local file, first call create_upload_urls, PUT the raw bytes as directed, and pass the resulting upload_id here. Staging does not change the active brand. To use the uploaded font, pass its font_asset_id and exact returned family in an exact profile typography change with create_brand_edit. Family matching is case-sensitive after trimming.

Pass exactly one of font_url or upload_id.

Args:

  • brand_session_id: Brand session ID from list_brands.

  • font_url: Public font URL, max 5MB.

  • upload_id: Completed temporary upload containing the font file.

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": {
      "brand_session_id": "<brand_session_id>"
    },
    "name": "upload_brand_font"
  }
}

Input Schema

NameRequiredDescriptionDefault
font_urlNoPublic URL of the custom font to stage for a Brand Edit. The file must be TTF, OTF, WOFF, or WOFF2 and no larger than 5MB. Supply this URL or upload_id, but not both.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
upload_idNoCompleted temporary upload containing the custom font to stage. Obtain its ID from create_upload_urls or get_file_picker_handoff, and supply it instead of font_url.
brand_session_idYesBrand session ID from `list_brands`.

Output Schema

NameRequiredDescriptionDefault
familyYesFont family name. Pass it unchanged as family in the typography change.
formatYesFont file format.
weightYesFont weight, or the default weight of a variable font.
variableYesWhether the file is a variable font.
expires_atYesExpiry timestamp for this single-use font asset. The consuming brand edit must finish preparing before this time; starting before expiry is not sufficient.
font_asset_idYesFont asset ID. Pass it as font_asset_id in a create_brand_edit typography change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and the description adds substantial context beyond them: a 24-hour expiry bound on the asset, the exact conditions under which the asset is destroyed (candidate stored, preparation fails, work goes stale), and the instruction to re-upload for a later edit. The stated single-use lifecycle is consistent with idempotentHint=false and the non-destructive framing matches staging-only behavior.

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 and return values, then the input paths, then the downstream usage step — a sensible progression. Some redundancy remains, notably the Args list restating schema descriptions and the exactly-one-of rule appearing in both prose and schema, but nothing is materially wasted.

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?

For a staged-upload tool with a 24-hour lifecycle, it covers the full workflow (URL vs. upload path, expiry and cleanup, handoff to create_brand_edit, case-sensitive family matching). An output schema exists, so the enumerated return fields are bonus rather than a gap-filler.

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 all four parameters are already documented, including llm_model. The description's Args block largely restates the schema text (brand_session_id from list_brands, 5MB URL cap, upload_id source), adding the exact-one-of constraint and family matching behavior but little semantic detail the schema lacks.

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?

Opening sentence gives a specific verb and resource ('Stage a single-use custom font for a brand edit') and scopes it as single-use staging rather than installation, which separates it from siblings like upload_image and create_upload_urls. It also names exactly what the tool returns, so an agent knows the output shape before opening the schema.

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 defines the two mutually exclusive input paths ('Pass exactly one of font_url or upload_id') and gives the prerequisite sequence for local files: create_upload_urls, PUT raw bytes, then pass upload_id. It also routes forward to create_brand_edit with the required font_asset_id and exact family, and states that staging does not change the active brand.

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