Skip to main content
Glama
Sign In
Photoshop-MCP-IMT

Photoshop-MCP-IMT

by Immersive-Media-Technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

photoshop_set_text_font

Set the font family and size of the active text layer using a PostScript name for consistent results across Photoshop UI languages. Optionally specify a display name or font size in points.

Instructions

Set font family and size for active text layer.

Prefer the PostScript name (e.g. "ArialMT"): it is the same in every Photoshop UI language. A display name (e.g. "Arial") also works but can be localized; an exact PostScript match wins. Use photoshop_list_fonts to discover available fonts.

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": {
      "fontName": "<fontName>"
    },
    "name": "photoshop_set_text_font"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNameYesFont PostScript name (preferred, language-independent) or display name (see photoshop_list_fonts)
fontSizeNoFont size in points (optional)
document_idNoOptional Photoshop document id from photoshop_get_state / photoshop_list_documents. When set, the tool activates that document before running so a UI tab switch cannot retarget the edit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a mutation scoped to the active text layer, but never states that it errors when the active layer isn't text, whether the font change is reversible (undo), or that omitting fontSize leaves size untouched. Useful but incomplete behavioral disclosure for a mutation tool.

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 target, then rationale for the naming convention, then the discovery hint. Well organized with no filler, though the PostScript/localization rationale could be tightened into a single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers the main usage pattern but leaves gaps: precondition failures, partial-update semantics (fontName only vs both), and confirmation of what changes are applied on the active layer.

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 coverage is 100% and the schema already documents PostScript vs display name for fontName, point units and optionality for fontSize, and the retargeting purpose of document_id. The description's only added nuance is the 'exact PostScript match wins' precedence rule, which is minor beyond the schema baseline.

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 specific verb and resource ('Set font family and size for active text layer'), distinguishing it from sibling text tools like photoshop_set_text_style, photoshop_set_text_ranges, and photoshop_set_text_color, which each target a different property.

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?

Clearly directs the agent to use photoshop_list_fonts for discovery and explains which font identifier form to prefer, which is real routing guidance. It does not cover the failure path (what to do if the active layer is not a text layer) or when to prefer the sibling style/range tools instead.

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