Playbook

Upload from URLs

upload_from_urls

Upload up to 100 assets in one call by giving Playbook public URLs to fetch. All assets land in the same board. Returns an array of skeleton assets immediately; the byte fetches run asynchronously per asset in the background. Requires a token with the write scope. Playbook fetches each URL itself, anonymously — links behind a login, expired signed URLs, and files that exist only on someone's machine cannot be ingested here. For those, use share_board with enable_uploads. It returns a link a person can drop files on without signing in, and whatever they add lands on that board for you to collect with list_assets. It needs a live human and it shows the board's existing contents to anyone holding the link, so reach for it only once no fetchable URL is available. Each fetch runs to a time budget (five minutes of streaming), so a source that is very large or very slow fails with "Source URL too large to fetch; upload manually" — when that happens, send those bytes yourself with create_upload_urls rather than retrying. Tip: validate collection_token with get_board first — an unknown token silently falls back to an anonymous default board.

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": {
      "collection_token": "<collection_token>",
      "assets": "<assets>"
    },
    "name": "upload_from_urls"
  }
}

Input Schema

Name	Required	Description
`assets`	Yes	Array of URL ingest specs (1-100 items)
`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.
`collection_token`	Yes	Destination board token (applied to every asset)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / assets / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / assets / items / properties / ai_agent_payload / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

Changed4 schema fields changedOct 5, 2026

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

changedInput schema / properties / assets / items / properties / ai_agent_payload / description

Previous value: -"Your own scratch space on this asset — prompt, model, seed, source job id, anything you need to recognise it in a later session. Playbook never interprets it. Max 4096 BYTES of serialised JSON; anything larger is REJECTED, never truncated. A write REPLACES the whole object. Readable per asset (get_asset, or list/search with get_ai_payload=true) but NOT searchable or filterable."New value: +"Free-form JSON metadata stored with the asset — for example generation settings such as model and seed, or a source job id. Playbook never interprets it. Max 4096 BYTES of serialised JSON; anything larger is REJECTED, never truncated. A write REPLACES the whole object. Readable per asset (get_asset, or list/search with get_ai_payload=true) but NOT searchable or filterable."

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: -[
-  "collection_token",
-  "assets",
-  "context"
-]New value: +[
+  "collection_token",
+  "assets"
+]

First observedOct 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only say this is a non-readonly, open-world, non-idempotent write. The description adds substantive behavior: skeleton assets return immediately while byte fetches run asynchronously, each fetch is anonymous and capped at a five-minute streaming budget with a specific failure string, and it discloses the silent fallback to an anonymous default board on an unknown collection_token. That last item is a real hazard the annotations cannot convey.

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?

The core mechanics, auth requirement, and failure path are front-loaded and each sentence carries information. The share_board digression runs long and could be tightened, and the trailing tip is a better fit before the alternative-workflow discussion, but there is no filler.

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 an asynchronous batch ingest tool with no output schema, the definition covers what is returned (skeleton assets, not bytes), how long fetches take, what failure looks like, what permissions are needed, and which tool to reach for on each of the two escape hatches. An agent can act correctly without further discovery.

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; the description still earns more by advising validation of collection_token via get_board to avoid the anonymous fallback, and by noting that every asset lands on the same board. It says nothing extra about the organization parameter, which the schema already covers well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb and resource ("Upload up to 100 assets in one call by giving Playbook public URLs to fetch") and scopes the batch to a single board, which implicitly separates it from the singular upload_from_url sibling. It never names that sibling explicitly, so the differentiation is inferable rather than stated.

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 rules in both directions: when no fetchable URL exists use share_board with enable_uploads (with the caveat that it needs a live human and exposes board contents), and when a fetch times out use create_upload_urls rather than retrying. It also warns that unauthenticated/expired/machine-local sources cannot be ingested here.

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?