Skip to main content
Glama

xtiles_get_content_by_link

Read-onlyIdempotent

Resolve any xTiles link to the content it points at. Use this whenever the user pastes an xTiles URL instead of guessing which id it contains — the same URL can address a whole page or a single tile depending on its query string. Handles page links (/{viewId}, /doc/{viewId}, /embed/{viewId} — any xTiles domain, public or custom), tile links (?nvi=, ?wfm=, ?scrollTo=) and "copy link" links (/links/{linkId}). The URL is parsed and resolved against your own xTiles content by our API — it is never fetched from the host it names, so this only ever reaches the caller's own xTiles resources. Returns resource_type (what the link turned out to be), the ids it resolved to, and the content of THAT resource — for a tile link, the tile's own markdown, not the whole page. To read the full page a tile belongs to, follow up with xtiles_get_view_content using the returned view_id. A link to a collection card resolves to that card and returns ITS content — a card and a tile are the same item wearing two hats, so the type is TILE. The response states what you may do with the resource; respect it before offering to edit. Leftover tracking parameters (utm_*, im_ref, …) are ignored — paste the link as-is. Errors: 400 the string is not an xTiles link; 422 the link is a recognised shape we cannot resolve yet (public forms, task screens, workspace links); 404 the page or link no longer exists; 403 no access — which is also the answer for an unknown collection row, since telling those two apart would leak whether a private id exists. Report a 403 as "no access, or it no longer exists", not as a definite refusal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAny xTiles link, passed EXACTLY as the user gave it — do NOT strip the query string. The query string is what distinguishes a link to a single tile from a link to the whole page: `https://xtiles.app/6740858058af8a09bf6096e6` is the page, while `https://xtiles.app/6740858058af8a09bf6096e6?nvi=eyJ2IjoxLC4uLg` addresses one tile inside it. Accepted: page links (`/{viewId}`, `/doc/{viewId}`, `/embed/{viewId}`), tile links (`?nvi=`, `?wfm=`, `?scrollTo=`) and "copy link to tile" links (`/links/{linkId}`). Any host works — public and custom xTiles domains included. A bare id is NOT a link and is rejected: an id alone does not say whether it names a page, a project or a task. If you already have a `viewId`, call `xtiles_get_view_content` instead. Returns the content of whatever the link addresses: for a tile link, that tile's content, not the page's.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
urlYes
titleNo
accessNo
contentNo
page_urlNo
collectionNo
page_titleNo
resource_urlNo
project_titleNo
resource_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that URLs are parsed and resolved locally against the caller's own resources and never fetched from the named host (openWorldHint=false context), explains the 400/422/404/403 error semantics, and instructs the agent to report 403 ambiguously to avoid leaking private-id existence. This is unusually rich, honoring real security and UX constraints.

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 purpose and usage, then structured into link shapes, resolution semantics, return values, and error codes. Dense but every sentence carries information. Slightly long for a one-parameter tool, but the density is warranted by the URL-shape complexity.

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?

Even though an output schema exists, the description adds the crucial interpretation layer the schema cannot: distinguishing resource_type=TILE for a card, clarifying that a tile link returns the tile's own markdown, pointing to the follow-up tool for the full page, and decoding the 403 ambiguity. Nothing an agent needs to call and interpret this tool 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?

Schema coverage is already 100%, with the schema itself explaining the query-string distinction between page and tile links. The description reinforces this with worked examples of accepted URL shapes and reiterates that a bare id is rejected. It adds semantic depth rather than restating 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 and resource ('Resolve any xTiles link to the content it points at') and explicitly distinguishes itself from the nearest sibling by naming xtiles_get_view_content as the correct tool when the user already has a viewId. The link-shape taxonomy makes the scope unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tells the agent exactly when to use it ('whenever the user pastes an xTiles URL instead of guessing which id it contains') and when not to route here ('If you already have a viewId, call xtiles_get_view_content instead', repeated in the description's follow-up guidance). The 'paste the link as-is' instruction removes a common failure mode.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources