Playbook

Create upload URLs

create_upload_urls

Batch form of create_upload_url: request upload addresses for up to 50 files in one call, then send each file's bytes and finish them all with finish_uploads. Give every item a uuid of your own — it is echoed back beside that item's address, and with several similar files it is the only reliable way to tell which address belongs to which file. Returns a batch_id that finish_uploads needs: it holds a reservation against the workspace's quota until the batch completes — so prepare a batch only when you are ready to finish it, and pass the batch_id back. Use upload_from_urls instead when the files are already at URLs Playbook can fetch. If any single file cannot be handled the whole call is refused rather than half of it succeeding.

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": {
      "files": "<files>"
    },
    "name": "create_upload_urls"
  }
}

Input Schema

Name	Required	Description	Default
`files`	Yes	Files to prepare (1-50)
`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
```
- removedInput schema / properties / files / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / files / items / properties / size / maximum
```
Added value: +9007199254740991
```
Changed2 schema fields changedOct 28, 2026
- changedInput schema / properties / files / description
```
Previous value: -"Files to prepare (1-100)"New value: +"Files to prepare (1-50)"
```
- changedInput schema / properties / files / maxItems
```
Previous value: -100New value: +50
```

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

First observedOct 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing that the returned batch_id holds a quota reservation until completion, that the call is all-or-nothing (refused rather than partially succeeding), and that size is checked against the storage allowance before signing. The only gap is that it doesn't state URL expiry or auth/permission requirements, so it stops just short of full behavioral coverage.

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 batch purpose and the finish_uploads dependency, then the uuid caveat, then the batch_id/quota warning, then the alternative tool. Dense and well-ordered, though the single long paragraph could be split for scanability and the uuid sentence is slightly verbose.

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?

There is no output schema, yet the description explains the return value (batch_id), its lifetime, and its required handoff to finish_uploads, plus the failure mode. For a two-parameter, quota-affecting batch tool, nothing an agent needs to call it correctly is missing.

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 already 100%, so the baseline is 3; the description earns extra by explaining why `uuid` matters ("the only reliable way to tell which address belongs to which file") and by framing the batch_id contract that ties into finish_uploads. It adds rationale rather than repeating field definitions.

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?

Opens with a specific verb+resource ("Batch form of create_upload_url: request upload addresses for up to 50 files in one call") and immediately distinguishes itself from the singular sibling and from upload_from_urls. An agent can identify the tool and its scope 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 Guidelines5/5

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

Explicitly routes the agent: use this for batches, use upload_from_urls when files already live at fetchable URLs, and prepare a batch only when ready to finish it. It also names the downstream tools (finish_uploads) required to complete the flow, so the whole workflow is inferable.

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?