Kulhad

Change my page details

update_profile

DestructiveIdempotent

Change the creator's name, bio, page address, kind of page (person or organisation), page language, dashboard language, and the links on the page. Only the fields you pass change. Links replace the whole list, so pass every link that should stay. The bio keeps bold, italic, links and line breaks and is cut at 280 characters. Changing the page address stops the old kulhad.co address working at once, with no redirect: printed QR codes, embeds and OBS overlay links break, and the old name is free for anyone to take. Not allowed while a custom domain is active. Writes to the creator's own Kulhad account only.

Input Schema

Name	Required	Description
`bio`	No	A short introduction. Bold, italic, links and line breaks are kept, everything else is stripped, and it is cut at 280 characters.
`kind`	No
`name`	No	The name shown on the page.
`socials`	No	Replaces the whole list. Pass an empty array to remove every link.
`username`	No	The page address, as in kulhad.co/priya. The old address stops working immediately with no redirect, and the old name becomes free. Cannot be changed while a custom domain is active.
`uiLanguage`	No	The creator dashboard language.
`pageLanguage`	No	The language the public page is written in.

Output Schema

Name	Required	Description	Default
`url`	Yes
`saved`	Yes
`dropped`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

changedInput schema / properties / bio / description

Previous value: -"A short introduction. Plain text; bold, italic and one link are kept, everything else is stripped."New value: +"A short introduction. Bold, italic, links and line breaks are kept, everything else is stripped, and it is cut at 280 characters."

changedInput schema / properties / username / description

Previous value: -"The page address, as in kulhad.co/priya. Cannot be changed while a custom domain is connected."New value: +"The page address, as in kulhad.co/priya. The old address stops working immediately with no redirect, and the old name becomes free. Cannot be changed while a custom domain is active."

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial value beyond annotations: it explains the immediate no-redirect breakage of the old address, QR/embed/overlay collateral damage, name release, custom-domain restriction, bio truncation at 280 chars, and link-list replacement. This goes well beyond destructiveHint/idempotentHint.

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?

Front-loaded with the field list then consequences; every sentence carries weight. Slightly dense but well-organized, with the highest-impact warning (address change) placed before lesser constraints.

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?

Given 7 optional params, destructive annotations, and an output schema, the description covers the mutation semantics, irreversibility, and replacement behaviors an agent needs. Return values are covered by the output schema so needn't be repeated.

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 86%, so the schema already documents most parameters including bio truncation and the username/custom-domain constraint. The description largely mirrors that and adds only the link-replace behavior, which is also in the schema.

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 states a precise verb + resource and enumerates every mutable field (name, bio, username, kind, page/ui language, socials). It is clearly distinguishable from sibling tools like update_page_appearance and update_seo.

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 clearly establishes partial-update semantics ('Only the fields you pass change') and flags the socials-replace rule. It doesn't explicitly route to siblings (e.g. check_username_available before username, or update_seo for SEO fields), leaving some alternative-selection gaps.

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

All Kulhad 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.

Resources

Need Help?