Bisque Presentations

Update channel

update_channel

Idempotent

Update one of your channels. Set the description — the line a stranger reads in a search result or a link unfurl, at most 160 characters, empty to clear it and go back to naming the newest presentations. Set the avatar from an image URL, which is fetched, center-cropped square and resized. Pass either or both. Omit handle to use your default channel.

Input Schema

TableJSON Schema

Name	Required	Description
`handle`	No	Which of your channel handles to update; defaults to your default username.
`image_url`	No	https URL of the avatar image (any common format, ≤10 MB).
`description`	No	What the channel publishes, in the owner's words. Empty clears it.

Output Schema

TableJSON Schema

Name	Required	Description
`failed`	No	Fields that did not apply, each with the reason. A field listed here left the channel unchanged; the ones in updated still took effect.
`handle`	Yes
`updated`	Yes	Field names that were written.
`channelUrl`	Yes	Public channel page carrying the update.
`description`	No	The stored line, or null when the write cleared it.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description discloses important behavior beyond the annotations: an empty description clears the channel description and restores a fallback naming behavior, and the avatar is fetched, center-cropped square, and resized. It also clarifies the default-handle behavior. None of this contradicts the annotations, and the added context materially helps an agent predict side effects.

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?

The description is compact and front-loaded: the core action appears first, followed by specific parameter behaviors and default handling. Every sentence contributes useful information, and there is no filler or repetition of schema details beyond what adds operational meaning.

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 mutation tool with three optional parameters and no required fields, the description covers the important scenarios: what each parameter does, how to clear the description, how avatar processing works, and what happens when handle is omitted. Since an output schema exists, explaining return values is unnecessary. Nothing essential is missing.

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?

Even though the input schema documents all parameters, the description adds meaning beyond it: it explains what a stranger sees in search results or link unfurls, that an empty description clears it, that the avatar image is center-cropped and resized, and that parameters can be passed either or both. The 'omit handle for default channel' note is also valuable.

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 opens with a specific verb and resource, 'Update one of your channels,' and then clearly enumerates exactly what can be updated: the description and the avatar. It is immediately distinguishable from the presentation-focused sibling tools and leaves no ambiguity about its scope.

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?

The description provides practical usage guidance: you can pass either or both of description and image URL, and omitting handle falls back to your default channel. It does not name an alternative because no sibling tool performs channel updates, but the guidance clearly covers the main decision points for calling it.

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

All Bisque Presentations tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Tools are grouped into clear resource families (artifacts, artifact threads, presentations, channels) and descriptions explicitly redirect between create_artifact and create_presentation. The main potential confusion is create_presentation vs publish_narrated_presentation, since both produce presentations but differ in narration source; the descriptions do clarify this.

Naming Consistency5/5

All tools use snake_case verb_noun naming with consistent families like get_artifact, get_artifact_thread, and get_presentation_spec. publish_narrated_presentation is longer but still follows the verb_noun pattern, and there are no mixed casing styles or erratic naming conventions.

Tool Count4/5

19 tools is above the typical 3-15 range, but the count is justified by four clear subdomains: artifacts, artifact threads, presentations, and channels. No tools are redundant, though the set is large enough to feel slightly heavy.

Completeness4/5

Artifacts have full CRUD plus sharing, and threads have create/read/list/reply/resolve. Presentations cover authoring spec, creation/publishing, status, analytics, and reading context, but there is no delete or explicit update endpoint for presentations and no exposed way to fetch mentionables; these are workable gaps rather than fatal ones.

Resources

Need Help?