AMZ Vault

PPC: Asset upload link

ppc_asset_upload_link

Read-only

Mint a 1-hour browser-upload link so the USER can hand over a local file (chat attachments cannot reach the server). Flow: call this → send upload_url to the user → they drop the file there (image jpg/png ≤25MB, or video mp4/mov/wmv/avi ≤100MB) → call stage_asset_upload with the returned staged_file_id. Videos over 100MB must be hosted at a public URL instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ppc_asset_upload_link"
  }
}

Input Schema

Name	Required	Description	Default
`profile_id`	No	Which advertising profile (see account_profiles). Optional when the token has exactly one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 5, 2026

TDQS

A4.4/5.0

Behavior5/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 adds valuable behavioral context: the link expires in 1 hour, chat attachments cannot reach the server, file type/size limits, the upload_url/staged_file_id flow, and the video-size exception. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact yet information-dense, with the core purpose front-loaded, then a flow, constraints, and an exception. Every sentence earns its place and there is no redundant fluff.

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?

Even without an output schema, the description names the key returned artifacts (upload_url and staged_file_id) and gives the complete handoff flow. It could be slightly more explicit about the exact response shape, but for a low-complexity tool the provided context is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional parameter profile_id is already fully described in the schema (100% coverage). The description adds no additional parameter-level detail, but because the schema carries the full burden, a baseline score of 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Mint a 1-hour browser-upload link.' It clearly distinguishes this tool from chat attachments and downstream stage_asset_upload, so an agent can understand exactly what action is being performed and why.

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

Usage Guidelines4/5

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

The description provides a clear step-by-step flow and states when this tool is appropriate (local file handover) versus when it is not (videos over 100MB must use a public URL). It does not explicitly name an alternative sibling tool for the public-URL case, so it slightly misses a fully explicit when-not-to-use comparison.

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

All AMZ Vault 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?