Skip to main content
Glama
Sign In

URLinks

by me.urlinks
OverviewDiscussionsAdmin

update_block

Destructive

Update block content/style by position or block_id.

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_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoFields merged into the block's style.
contentNoFields merged into the block's content, e.g. { label, url } for a link.
block_idNoID of the block to update. Give this or position.
positionNo0-based index of the block to update (see get_profile). Give this or block_id.
link_layoutNoLink blocks: 'feature' shows a large image card (needs an image on the link); 'standard' is a normal button.
hover_effectNoEffect when the pointer hovers over the block.
link_animationNoAttention animation on the block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / block_id / description
      Added value: +"ID of the block to update. Give this or position."
    • addedInput schema / properties / content / description
      Added value: +"Fields merged into the block's content, e.g. { label, url } for a link."
    • addedInput schema / properties / hover_effect / description
      Added value: +"Effect when the pointer hovers over the block."
    • addedInput schema / properties / link_animation / description
      Added value: +"Attention animation on the block."
    • addedInput schema / properties / link_layout / description
      Added value: +"Link blocks: 'feature' shows a large image card (needs an image on the link); 'standard' is a normal button."
    • addedInput schema / properties / position / description
      Added value: +"0-based index of the block to update (see get_profile). Give this or block_id."
    • addedInput schema / properties / style / description
      Added value: +"Fields merged into the block's style."
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the mutation risk is already flagged, but the description adds nothing about what 'destructive' means here — whether omitted fields are preserved, whether content/style objects are merged or replaced, or whether the update is reversible. For a destructive 7-parameter mutation, the one-line description leaves the risk profile unexplained.

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?

A single front-loaded sentence with no filler, and the two addressing modes are stated up front. It is efficient but borders on under-specification given the tool's complexity.

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?

With 7 parameters, nested style/content objects, three enums, destructive semantics, and no output schema, the description should at minimum explain merge behavior and that exactly one of block_id/position is expected (required list is empty, so an agent could call with neither). None of that is 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%, including per-field docs for style/content merge semantics, the enums for link_layout, hover_effect, and link_animation, and the 'give this or block_id' exclusivity notes. The description only repeats the position/block_id addressing already documented in the schema, so 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?

The description states a specific verb (update) and resource (block) plus the two addressing modes (position or block_id), which lets an agent separate it from add_block, remove_block, and reorder_blocks. It stops short of naming or contrasting 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 Guidelines2/5

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

There is no guidance on when to use this tool versus add_block, reorder_blocks, or update_page_style, and no note that position values come from get_profile (only the schema hints at that). The agent must infer the workflow entirely.

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

All URLinks 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