Skip to main content
Glama

update_person_channel

Idempotent

Update a contact channel for a person. Identify the channel by ID or provider+value, then optionally change the provider or value.

Instructions

Update one contact channel on a person. Person accepts person ID, exact email, or exact display name. Identify the channel with exactly one locator: channelId, or provider plus value. Provide newProvider, newValue, or both. Updating to an existing provider+value on the same person fails with a conflict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelIdNoa string that will be trimmed
providerNoChannel provider label: email, phone, linkedin, twitter, github, facebook, telegram, homepage, whatsapp, skype, profile, viber.
valueNoa string that will be trimmed
personYesa string that will be trimmed
newProviderNoChannel provider label: email, phone, linkedin, twitter, github, facebook, telegram, homepage, whatsapp, skype, profile, viber.
newValueNoa string that will be trimmed

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior4/5

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

Annotations declare idempotentHint=true, non-destructive, non-readOnly. Description adds that updating to an existing provider+value fails with conflict, a key behavioral trait beyond annotations.

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?

Four focused sentences, front-loaded with action, no fluff. Each sentence serves a purpose: what, person identification, channel identification, new values, and failure case.

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?

Covers identification rules, update semantics, and error condition. With output schema present, return values need not be detailed. Complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema: clarifies person parameter accepts ID, email, or display name; explains channel locator constraints (exactly one); specifies newProvider/newValue requirements. Schema coverage is 100%, but description still adds value.

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 clearly states 'Update one contact channel on a person', with specific verbs and resource. It distinguishes from siblings like add/remove person channel by using 'update'.

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?

Provides clear guidance on person identification (ID, email, display name), channel identification (channelId or provider+value), and what new values to provide. Mentions conflict failure case. Does not explicitly list when not to use, but context with siblings is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dearlordylord/huly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server