Playbook

Get asset permalinks

get_asset_permalinks

Read-only

Read the permanent public URL of one or more assets, optionally rendered at a size you choose. Reads only — it never publishes anything, so an asset that has no permalink yet is reported under not_published; run add_asset_permalinks on those first. An asset under pending is still being published: its URL is withheld until the file is in place, so read it again shortly instead of publishing it again. This is the URL to use anywhere the link has to outlive the session: a document, a deck, a web page, a hand-off to another system. For a throwaway image to look at right now, use get_asset_previews instead — it needs no permalink and costs no quota. width/height resize IMAGES only (one of the two keeps the aspect ratio); PDFs, video and everything else are served at their stored size and ignore both.

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": {
      "asset_tokens": "<asset_tokens>"
    },
    "name": "get_asset_permalinks"
  }
}

Input Schema

Name	Required	Description
`width`	No	Render images this wide, in pixels
`height`	No	Render images this tall, in pixels
`asset_tokens`	Yes	Asset tokens to read (max 1000)
`organization`	No	Workspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / height / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / width / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedOct 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "asset_tokens",
-  "context"
-]New value: +[
+  "asset_tokens"
+]

First observedOct 2, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description nonetheless adds real behavioral context: it never publishes, unpublished assets surface under `not_published`, and `pending` withholds the URL until the file lands. That is useful, but a 3 reflects that these are response-state notes layered on an already-annotated read, and the shape of the returned URL map (one per token? failures intermixed?) is left unstated.

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 the core action and the failure mode, then the alternative, then parameter caveats — a sensible ordering. It is dense and nearly every clause carries information, though the 'document, a deck, a web page, a hand-off' enumeration is decorative filler that could be trimmed.

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 helpfully names the `not_published` and `pending` states an agent will encounter. It is slightly thin on what a mixed-batch response looks like when some tokens resolve and others do not, which is a realistic case given minItems 1 / maxItems 1000.

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 100%, so the baseline is 3, but the description goes beyond it: `width`/`height` resize IMAGES only, exactly one of the two preserves aspect ratio, and PDFs, video and other types are served at stored size and ignore both. That constraint is not expressible in the schema and prevents a wasted or misleading resize call.

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 — 'Read the permanent public URL of one or more assets' — with the added scope 'optionally rendered at a size you choose'. It is immediately distinguishable from add_asset_permalinks, remove_asset_permalinks, and get_asset_previews without opening any schema.

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?

Gives explicit routing in both directions: run add_asset_permalinks first for assets reported under `not_published`, and use get_asset_previews for a throwaway image because it needs no permalink and costs no quota. It also names the selection criterion for this tool — links that must outlive the session.

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

All Playbook tools Inspect

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

Need Help?