URLinks

update_page_style

Destructive

Merge visual/layout fields into page_style. Syncs displayName/bio/avatarUrl to top-level profile when set.

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": "update_page_style"
  }
}

Input Schema

Name	Required	Description
`bio`	No	Short bio shown under the name.
`bio_color`	No	Bio text color (CSS color).
`block_gap`	No	Space between blocks in px.
`max_width`	No	Maximum width of the content column in px (default 600).
`name_font`	No	Display name font. See list_profile_style_options for available fonts.
`avatar_url`	No	Avatar image URL.
`banner_url`	No	Banner image URL.
`name_color`	No	Display name color (CSS color).
`page_style`	No	Raw page_style fields (camelCase keys) merged as-is. The named arguments below override the same fields.
`avatar_shape`	No	Avatar image shape.
`button_color`	No	Link button color (CSS color).
`button_style`	No	Link button style.
`default_font`	No	Body font. See list_profile_style_options for available fonts.
`display_name`	No	Name shown at the top of the profile.
`button_radius`	No	Link button corner radius in px (default 10).
`content_align`	No	Alignment of the page content.
`header_layout`	No	'hero' shows a larger, centered avatar and name; 'normal' is the default.
`reduce_motion`	No	Set true to keep animated background scenes still.
`profile_layout`	No	'gallery' shows only gallery blocks; 'standard' shows every block.
`show_link_icons`	No	Show site icons on link buttons (default true).
`background_color`	No	Page background color (CSS color, e.g. #F4F1EA).
`background_scene`	No	Animated background scene. Replaces any background gradient or image.
`background_scrim`	No	Darkening layer over photo backgrounds for legibility. On by default; set false to remove it.
`bio_stroke_color`	No	Bio outline color (CSS color).
`bio_stroke_width`	No	Outline width around the bio letters, 0-3 px.
`banner_full_bleed`	No	Banner spans the full page width by default; set false to fit it to the content column.
`button_text_color`	No	Link button text color (CSS color).
`name_stroke_color`	No	Display name outline color (CSS color).
`name_stroke_width`	No	Outline width around the display name letters, 0-3 px.
`social_icon_style`	No	Social icons in brand colors, theme colors, or outline.
`background_texture`	No	Texture overlaid on the background.
`default_text_color`	No	Default text color for the page (CSS color).
`background_gradient`	No	Background gradient: type, optional angle, and color stops at positions 0-1. Replaces any scene or image.
`clear_background_scene`	No	Set true to remove the current background scene.

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedNov 8, 2026

addedInput schema / properties / avatar_shape / description
```
Added value: +"Avatar image shape."
```
addedInput schema / properties / avatar_url / description
```
Added value: +"Avatar image URL."
```

addedInput schema / properties / background_color / description

Added value: +"Page background color (CSS color, e.g. #F4F1EA)."

addedInput schema / properties / background_gradient / description

Added value: +"Background gradient: type, optional angle, and color stops at positions 0-1. Replaces any scene or image."

addedInput schema / properties / background_scene / description

Added value: +"Animated background scene. Replaces any background gradient or image."

addedInput schema / properties / background_scrim / description

Added value: +"Darkening layer over photo backgrounds for legibility. On by default; set false to remove it."

addedInput schema / properties / background_texture / description
```
Added value: +"Texture overlaid on the background."
```

addedInput schema / properties / banner_full_bleed / description

Added value: +"Banner spans the full page width by default; set false to fit it to the content column."

addedInput schema / properties / banner_url / description
```
Added value: +"Banner image URL."
```

addedInput schema / properties / bio / description

Added value: +"Short bio shown under the name."

addedInput schema / properties / bio_color / description
```
Added value: +"Bio text color (CSS color)."
```
addedInput schema / properties / bio_stroke_color / description
```
Added value: +"Bio outline color (CSS color)."
```

addedInput schema / properties / bio_stroke_width / description

Added value: +"Outline width around the bio letters, 0-3 px."

addedInput schema / properties / block_gap / description
```
Added value: +"Space between blocks in px."
```
addedInput schema / properties / button_color / description
```
Added value: +"Link button color (CSS color)."
```

addedInput schema / properties / button_radius / description

Added value: +"Link button corner radius in px (default 10)."

addedInput schema / properties / button_style / description
```
Added value: +"Link button style."
```
addedInput schema / properties / button_text_color / description
```
Added value: +"Link button text color (CSS color)."
```
addedInput schema / properties / clear_background_scene / description
```
Added value: +"Set true to remove the current background scene."
```
addedInput schema / properties / content_align / description
```
Added value: +"Alignment of the page content."
```

addedInput schema / properties / default_font / description

Added value: +"Body font. See list_profile_style_options for available fonts."

addedInput schema / properties / default_text_color / description
```
Added value: +"Default text color for the page (CSS color)."
```
addedInput schema / properties / display_name / description
```
Added value: +"Name shown at the top of the profile."
```

addedInput schema / properties / header_layout / description

Added value: +"'hero' shows a larger, centered avatar and name; 'normal' is the default."

addedInput schema / properties / max_width / description

Added value: +"Maximum width of the content column in px (default 600)."

addedInput schema / properties / name_color / description
```
Added value: +"Display name color (CSS color)."
```

addedInput schema / properties / name_font / description

Added value: +"Display name font. See list_profile_style_options for available fonts."

addedInput schema / properties / name_stroke_color / description
```
Added value: +"Display name outline color (CSS color)."
```

addedInput schema / properties / name_stroke_width / description

Added value: +"Outline width around the display name letters, 0-3 px."

addedInput schema / properties / page_style / description

Added value: +"Raw page_style fields (camelCase keys) merged as-is. The named arguments below override the same fields."

addedInput schema / properties / profile_layout / description

Added value: +"'gallery' shows only gallery blocks; 'standard' shows every block."

addedInput schema / properties / reduce_motion / description

Added value: +"Set true to keep animated background scenes still."

addedInput schema / properties / show_link_icons / description

Added value: +"Show site icons on link buttons (default true)."

addedInput schema / properties / social_icon_style / description

Added value: +"Social icons in brand colors, theme colors, or outline."

First observedNov 8, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The annotations flag destructiveHint=true, yet the description never says what may be destroyed or overwritten; only the schema notes (e.g., background_scene replaces any gradient or image) carry that. The description does add real value beyond annotations by disclosing the propagation of displayName/bio/avatarUrl to the top-level profile, a side effect an agent would otherwise miss.

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?

Two compact sentences with the mutation front-loaded and no filler. It is arguably too terse for a 34-parameter, destructive tool, but the text itself contains no wasted wording.

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

Completeness2/5

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

Given 34 optional parameters, nested objects, a destructive annotation, and no output schema, the two-sentence description leaves significant gaps: no mention of overwrite/replacement risk, no pointer to list_profile_style_options (only present in the schema), and no routing guidance among related styling tools.

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%, with detailed per-field descriptions, enums, and the explicit precedence note that named arguments override page_style keys. The description adds nothing beyond that structured information, so the baseline of 3 applies despite the large 34-parameter surface.

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 uses a specific verb-plus-resource pairing ('Merge visual/layout fields into page_style') and adds the notable side effect of syncing displayName/bio/avatarUrl to the top-level profile. The purpose is clear, but it does not distinguish the tool from siblings such as update_profile or apply_theme/set_theme, which also touch styling and profile data.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to choose this tool over update_profile or apply_theme, nor any statement of prerequisites or exclusions. The word 'merge' implies partial-update semantics, but that inference is the only usage signal offered.

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

All URLinks tools Inspect

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.