Globestudio

Build a share link

build_share_url

Read-onlyIdempotent

Create or edit a Globestudio globe link by choosing a preset look or changing only needed settings; returns share and embed URLs.

Instructions

Build Globestudio URLs for a customized globe. Start from a preset (look) or change an existing link (share_url, e.g. one the user pasted): pass only the settings to change and everything else in the link is kept. Returns share_url (opens the studio with those settings) and embed_url (the bare canvas, for iframes).

Input Schema

TableJSON Schema

Name	Required	Description
`look`	No	Preset id, e.g. 'halftone'. Required unless share_url is given.
`shape`	No
`config`	No	Any other setting, using the keys read_share_url returns in config, e.g. {"viewMode": "flat"} or {"globeSettings": {"autoSpin": false}}. {"viewSwitch": true} gives the embed a Globe and Map switch in its corner, so visitors can turn the globe into the flat map and back. Nested settings merge key by key; keys Globestudio does not accept come back in ignored. With "v": 3, as read_share_url returns for a link that has it, its colors render as their hex; without it they render darker, as in links before v3.
`density`	No
`dotColor`	No	Hex color, e.g. '#3df4ff'.
`selection`	No	Region: 'world' (default), ISO country code ('JP' or 'JPN'), country name ('Japan'), continent ('Europe'), or subregion ('Western Europe').
`share_url`	No	A Globestudio link to change instead of starting from a preset.
`background`	No	Background hex.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.2Oct 18, 2026

changedInput schema / properties / config / description

Previous value: -"Any other setting, using the keys read_share_url returns in config, e.g. {\"viewMode\": \"flat\"} or {\"globeSettings\": {\"autoSpin\": false}}. Nested settings merge key by key; keys Globestudio does not accept come back in ignored. With \"v\": 3, as read_share_url returns for a link that has it, its colors render as their hex; without it they render darker, as in links before v3."New value: +"Any other setting, using the keys read_share_url returns in config, e.g. {\"viewMode\": \"flat\"} or {\"globeSettings\": {\"autoSpin\": false}}. {\"viewSwitch\": true} gives the embed a Globe and Map switch in its corner, so visitors can turn the globe into the flat map and back. Nested settings merge key by key; keys Globestudio does not accept come back in ignored. With \"v\": 3, as read_share_url returns for a link that has it, its colors render as their hex; without it they render darker, as in links before v3."

Changed1 schema field changedv1.2.0Oct 5, 2026

changedInput schema / properties / config / description

Previous value: -"Any other setting, using the keys read_share_url returns in config, e.g. {\"viewMode\": \"flat\"} or {\"globeSettings\": {\"autoSpin\": false}}. Nested settings merge key by key; keys Globestudio does not accept come back in ignored."New value: +"Any other setting, using the keys read_share_url returns in config, e.g. {\"viewMode\": \"flat\"} or {\"globeSettings\": {\"autoSpin\": false}}. Nested settings merge key by key; keys Globestudio does not accept come back in ignored. With \"v\": 3, as read_share_url returns for a link that has it, its colors render as their hex; without it they render darker, as in links before v3."

First observedv0.2.0Sep 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint and non-destructive, so safety is covered. The description adds real value beyond them by disclosing the merge behavior ('pass only the settings to change and everything else in the link is kept') and, since there is no output schema, what the call returns and how the two URLs differ (studio vs bare canvas for iframes).

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?

Two tight sentences, front-loaded with the purpose and followed by the mode selection and return values. Dense but nearly every clause carries information; no filler or repetition of structured fields.

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

Completeness4/5

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

With no output schema, the description correctly fills the return-value gap (share_url vs embed_url) and covers the two invocation modes for an 8-parameter tool with a nested config object. Remaining details (ignored-key handling, v3 color behavior) live in the schema, so the description is sufficiently complete.

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

Parameters4/5

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

Schema coverage is 75% (only 'shape' and 'density' are undocumented) and the config parameter is richly annotated. The description still adds meaning beyond the schema by explaining the relationship between 'look' and 'share_url' and the partial-update/merge semantics of passing only changed settings.

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?

Names a specific verb and resource (build Globestudio URLs / share links) and immediately scopes the two operating modes: start from a preset via 'look' or modify an existing link via 'share_url'. This implicitly distinguishes it from the read-oriented sibling read_share_url, so an agent can tell what this tool does without opening the 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?

Gives clear routing for the two entry paths ('Start from a preset (look) or change an existing link (share_url, e.g. one the user pasted)') plus the key usage rule that only changed settings need to be passed. It lacks explicit when-not guidance or named alternatives (read_share_url, preview_url), so it stops short of a 5.

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

Deploy Server

Build a share link

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools