Skip to main content
Glama
Sign In

URLinks

by me.urlinks
OverviewDiscussionsAdmin

add_block

Add a block to the profile. Blocks appear in order — new blocks are added at the end by default, or at a specific position. Block types: link (clickable button), header (section heading), text (paragraph), divider (visual separator), image (full-width image), embed (YouTube/Spotify/SoundCloud), spacer (vertical gap), marquee (scrolling text).

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

Input Schema

NameRequiredDescriptionDefault
urlNoFor link blocks: the destination URL. For embed blocks: the video/music URL. For image blocks: the image source URL.
textNoFor text blocks: the content (supports basic HTML: <b>, <i>, <a>, <br>). For marquee blocks: the scrolling text.
typeYesBlock type
labelNoFor link blocks: the button text. For header blocks: the heading text.
positionNoInsert at this position (0-based). Omit to add at the end.
descriptionNoFor link blocks: optional subtitle shown below the label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare this is a non-read-only, non-destructive write, and the description adds ordering behavior (appended at end by default, or inserted at a position) plus the full type catalog. It does not disclose what happens on an out-of-range position, which fields are required per block type, or what is returned, so the behavioral picture remains partial.

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?

The core action and ordering rule are front-loaded in the first sentence, with the type catalog after it. The parenthetical glosses are slightly verbose but each one genuinely disambiguates a block type, so little is wasted.

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?

With 6 params, one required field, full schema coverage and no output schema, the description covers the essentials but leaves the sibling-overlap question and per-type validation behavior unanswered. For a creation tool whose misuse is mostly 'wrong type / missing field', that gap matters.

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 the schema already explains url, text, label, description and position per block type. The description's type list reinforces which types exist but adds no per-type field requirements beyond what the schema states, so it sits at the baseline.

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 to the profile') and enumerates the supported block types with plain-language glosses. It does not, however, distinguish itself from the sibling add_block_v2, nor from remove_block/update_block/reorder_blocks, which leaves a real ambiguity for an agent choosing between the two add variants.

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

Usage Guidelines3/5

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

Usage is only implied: the description explains the default append behavior and that a position can be supplied, which hints at when to use it. There is no explicit when-to-use/when-not guidance and no mention of the obvious alternative add_block_v2, which is a meaningful omission given how similar the names are.

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