Skip to main content
Glama
Sign In

DexURL

by com.dexurl
OverviewDiscussionsAdmin

Add links to a DexURL Bio page

add_to_bio_page
Idempotent

Add 1 to 50 links to a Bio page. On a published page the links go into its draft, which is not live until the owner presses Publish in the app; on an unpublished page they go straight onto the page. The connector never publishes a page. Addresses already on the page are skipped.

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": {
      "handle": "<handle>",
      "items": "<items>"
    },
    "name": "add_to_bio_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
handleYesThe Bio page handle, e.g. my-page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag a non-read, non-destructive, idempotent, open-world write. The description goes beyond them by explaining that on published pages writes land in a draft that is not live until the owner publishes, that the connector itself never publishes, and that already-present addresses are skipped — all material consequences an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and batch limit, then the publish/draft consequences, then the duplicate rule. Every sentence carries distinct information with no filler.

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

Completeness4/5

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

For a 2-parameter bulk write with no output schema, the description covers the important unknowns: what happens on published vs unpublished pages, that publishing is left to the owner, and duplicate handling. Only auth/ownership requirements and any result summary are unaddressed.

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 50% and the schema already documents url, title and handle. The description adds the useful behavioral note that duplicate addresses are skipped, which clarifies the semantics of the items array, but it says nothing extra about handle format beyond the schema's example.

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 and resource ('Add ... links to a Bio page') plus a hard batch bound of 1 to 50. It implicitly separates itself from single-link creation siblings by emphasizing bulk addition, though it never names an alternative tool outright.

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 context is implied by the draft-vs-live explanation, which tells the agent this is a non-publishing bulk write. However, there is no explicit 'use this instead of create_link when...' routing, and no stated prerequisites such as ownership or permissions on the handle.

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

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