Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Create upload URLs

create_upload_urls

Batch form of create_upload_url: request upload addresses for up to 100 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesFiles to prepare (1-100)
organizationNoWorkspace 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.

  1. Changed3 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive mutation, but the description adds substance beyond them: the returned batch_id holds a reservation against the workspace quota until completion, and the call is all-or-nothing ('if any single file cannot be handled the whole call is refused'). The uuid echo behavior is also disclosed. Lacks return-shape detail, which is minor.

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?

Purpose, mechanics, the uuid rationale, the batch_id/quota warning, and the alternative are all front-loaded into one dense paragraph with no filler sentences. Slightly long, but every clause carries operational weight.

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 a mutation tool with no output schema, the description covers the return value (batch_id), the cross-call dependency (finish_uploads), the quota/cost implication, and the failure mode. An agent has everything needed to call it correctly without opening other tools.

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 genuinely adds rationale the schema lacks: why a caller-supplied uuid matters ('with several similar files it is the only reliable way to tell which address belongs to which file') and why the batch_id must be passed back. It also reinforces the 'measure, do not estimate' size constraint.

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 ('request upload addresses for up to 100 files in one call') and explicitly frames itself as the batch form of create_upload_url. The agent can immediately distinguish it from the singular sibling and from upload_from_urls.

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 when-to-use ('prepare a batch only when you are ready to finish it'), a named alternative with the condition that selects it ('Use upload_from_urls instead when the files are already at URLs Playbook can fetch'), and the required follow-up call (finish_uploads). Nothing is left to inference.

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

All Playbook toolsInspect
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