Skip to main content
Glama
Sign In

Bloom

by diy.bloom.api
OverviewDiscussionsAdmin

Get a shareable app link

get_link
Read-onlyIdempotent

Resolve a project, page, frame, comment thread, comment or notification ID to the app's shareable Bloom URL. Returns url, equivalent to Copy link. Links address the project's preview branch; deleted targets or targets existing only on another branch return errors. Scope: project:read.

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": {
      "id": "<id>"
    },
    "name": "get_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAny id you already hold: a projectId, canvasPageId, frameId, threadId, commentId, or notificationId. No need to say which — the kind is detected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful beyond-schema context: links point at the project's preview branch, and deleted or other-branch targets return errors rather than a link. It stops short of describing response shape beyond "url" or any rate limiting, keeping it out of the top band.

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 tight sentences: capability first, then return value, then edge-case behavior and scope. Every clause carries information an agent would otherwise have to guess.

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 one-parameter, no-output-schema tool with rich annotations, the description supplies the missing pieces: what comes back (a URL), what it is equivalent to, and how failures manifest. Nothing an agent needs in order to call it correctly is absent.

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 100% and the parameter description already explains the polymorphic ID detection. The description restates the same ID kinds in prose, which is consistent but adds no syntax, format, or validation detail beyond 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?

States a specific verb ("Resolve") and resource (an ID to the app's shareable Bloom URL), then enumerates exactly which ID kinds it accepts. No sibling in the tool list does anything comparable, so an agent can pick it without cross-referencing.

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?

Usage is clearly implied and reinforced: give it any ID you already hold, and the result is "equivalent to Copy link." It also names the boundary conditions (deleted targets, targets on another branch) that make it fail, though it never explicitly says when to reach for a sibling instead.

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

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