URLinks

add_block_v2

Add a block with full prototype parity (gallery, countdown, product, embed presets).

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": {
      "type": "<type>"
    },
    "name": "add_block_v2"
  }
}

Input Schema

Name	Required	Description
`url`	No	Link destination (required for link blocks), or the image, embed, or product checkout URL.
`text`	No	Text for text, header, marquee, and countdown blocks.
`type`	Yes	Kind of block to add.
`label`	No	Link button text (required for link blocks). Also used as header text, image alt text, or countdown label.
`price`	No	Product price, e.g. "29" (product blocks).
`style`	No	Style fields for the new block.
`title`	No	Product name (product blocks).
`currency`	No	Currency symbol shown with the price, e.g. "$" (product blocks).
`position`	No	0-based index to insert the block at. Defaults to the end.
`target_iso`	No	Countdown end as an ISO 8601 date-time (countdown blocks). Defaults to one week from now.
`description`	No	Optional subtitle under a link block's label.
`link_layout`	No	Link blocks: 'feature' shows a large image card; 'standard' is a normal button.
`embed_preset`	No	Embed blocks: a Google Maps map, a booking page, or a form.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedNov 8, 2026

addedInput schema / properties / currency / description

Added value: +"Currency symbol shown with the price, e.g. \"$\" (product blocks)."

addedInput schema / properties / description / description

Added value: +"Optional subtitle under a link block's label."

addedInput schema / properties / embed_preset / description

Added value: +"Embed blocks: a Google Maps map, a booking page, or a form."

addedInput schema / properties / label / description

Added value: +"Link button text (required for link blocks). Also used as header text, image alt text, or countdown label."

addedInput schema / properties / link_layout / description

Added value: +"Link blocks: 'feature' shows a large image card; 'standard' is a normal button."

addedInput schema / properties / position / description

Added value: +"0-based index to insert the block at. Defaults to the end."

addedInput schema / properties / price / description

Added value: +"Product price, e.g. \"29\" (product blocks)."

addedInput schema / properties / style / description
```
Added value: +"Style fields for the new block."
```

addedInput schema / properties / target_iso / description

Added value: +"Countdown end as an ISO 8601 date-time (countdown blocks). Defaults to one week from now."

addedInput schema / properties / text / description

Added value: +"Text for text, header, marquee, and countdown blocks."

addedInput schema / properties / title / description
```
Added value: +"Product name (product blocks)."
```
addedInput schema / properties / type / description
```
Added value: +"Kind of block to add."
```

addedInput schema / properties / url / description

Added value: +"Link destination (required for link blocks), or the image, embed, or product checkout URL."

First observedNov 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that: it does not say whether unknown block types error out, whether a block id is returned, or what 'prototype parity' actually means operationally.

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. Its only weakness is jargon ('full prototype parity') that carries no meaning for an agent without prior context.

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 13-parameter mutation tool with a nested free-form 'style' object and no output schema, the description is thin: it doesn't indicate what is returned or how the style object is interpreted. The rich schema and annotations fill most of the gap, but the v1/v2 relationship remains unexplained.

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% across 13 parameters, including per-block applicability notes for url, label, text, target_iso, and embed_preset, so the baseline is 3. The description only gestures at the parameter space via the four named block families and adds no meaning beyond the schema.

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?

States a specific verb and resource ('Add a block') and names the block families it covers (gallery, countdown, product, embed presets). However, it never explains how this differs from the sibling tool 'add_block', which is the single most important thing an agent needs to know before choosing between them.

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 instead of the sibling 'add_block', nor any exclusions or prerequisites. The phrase 'full prototype parity' vaguely implies a superset of capability but leaves the agent to guess whether add_block is deprecated or still preferred for basic block types.

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.