URLinks

update_profile

Destructive

Update the profile's basic info — display name, bio, or avatar URL. Only the fields you provide will change; everything else stays the same. This does NOT publish the profile — use publish_profile for that.

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

Input Schema

Name	Required	Description
`bio`	No	Short bio text (max 160 chars)
`avatar_url`	No	URL of the avatar image (must be an S3/CloudFront URL from upload)
`display_name`	No	Display name shown on the profile (max 100 chars)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations declare a non-read-only, destructive operation, and the description adds meaningful behavior beyond them: this is a partial update where unspecified fields remain unchanged, and it does not publish the profile. It does not describe permission requirements or failure modes, but it substantially clarifies mutation semantics.

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 with no filler. The core operation is front-loaded, the partial-update behavior follows, and the publish_profile exclusion is placed last for quick routing.

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

Completeness5/5

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

For a simple three-parameter update tool with full schema descriptions, the definition covers the essential behavior: what changes, what stays fixed, and what not to confuse it with. No output schema exists, and none is needed for this description to be complete.

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 documents each parameter. The description names the same fields but does not add format, validation, or interaction details beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: update the profile's basic info. It lists the exact fields affected (display name, bio, avatar URL) and explicitly distinguishes itself from publish_profile, so an agent can separate it from siblings like update_page_style or publish_profile without opening any schema.

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

Usage Guidelines4/5

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

It gives clear usage context by naming the alternative for publishing (publish_profile) and stating that only supplied fields are changed. It does not provide exclusions for every sibling, but the field list makes the boundary clear enough for correct selection.

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.